Resolve inconsistency with import paths between development and production environments

[komalg1]

We are encountering an issue with module import paths that behave differently in our development and production environments. This inconsistency affects the reliability of our deployment process and could potentially lead to runtime errors.

Issue Details:
When using absolute import statements such as:
from backend.batch.utilities.helpers.EnvHelper import EnvHelper
the application functions correctly in the local development environment. However, in the production environment, the same path causes import errors, and the system requires a relative import path, like:
from ..helpers.EnvHelper import EnvHelper

Tasks:

• Determine why absolute paths fail in the production environment but work in development.
• Implement a solution that supports both absolute and relative import paths in all environments, thereby standardizing our codebase and deployment process.

[Prasanjeet-Microsoft]

As per the discussion with @adamdougal , we will continue to investigate on this issue and will see if any solution arise in the future that supports both absolute and relative import paths in all environments, will keep this issue open and update in case if any solutions found. FYI @Roopan-Microsoft