Add `atmos.yaml` configuration setting to enable/disable Terraform workspaces for Atmos components @Cerebrovinny @aknysh (#1073)

what

• Add atmos.yaml configuration setting to enable/disable Terraform workspaces for Atmos components
• Update docs

why

• Allow enabling/disabling Terraform workspaces for Atmos components by using the components.terraform.workspaces_enabled setting in atmos.yaml. If Terraform workspaces are disabled, the default workspace is used
• Don't generate Terraform workspace for the backend of type http (it does not support TF workspaces)

Fix `ATMOS_CLI_CONFIG_PATH` and `ATMOS_BASE_PATH` handling @haitham911 (#1096)

What

• Ensure that ATMOS_BASE_PATH is always set to an absolute path.
• Update the logic for ATMOS_CLI_CONFIG_PATH to store the directory of the config file instead of the file path itself.
• Adjust how environment variables are appended in both Terraform and Helmfile execution logic.
• Modify test cases and snapshot outputs to reflect the corrected behavior.

Why

• Previously, ATMOS_BASE_PATH could be set to a relative path, which could cause inconsistencies in resolving paths for components and stacks.
• ATMOS_CLI_CONFIG_PATH was being stored as the file path rather than the directory, leading to incorrect assumptions about where the config should be read from.
• The changes ensure that Atmos behaves consistently across different execution contexts and environments.

Add component completion to docs command @RoseSecurity (#1090)

what

• Add component completion to atmos docs command

why

• Enhance the user experience by providing autocomplete for the component’s documentation, making it easier to find relevant information

Loosen `Go` lint rules @osterman (#1084)

what

• Loosen some Go lint rules
• Added check to enforce consistent log alias

why

• Observed other PRs like: #1077