IN-928 Restructure the config module to use a 'Config' class

[jonavellecuerdo]

What does this PR do?

Refactor config module to use a Config class to improve code readability and flow.
The CLI main() method was also updated to exit cleanly in the event of failed
connection tests.

Helpful background context

• Updating the CLI main() method

  • During testing, it was discovered that the Traceback was printing twice in the CloudWatch logs.
  • In order to address this issue, the following updates were made:
    • Wrap each connection test in a try-except block;
    • Moving the wrapped code into a function in carbon.app.run_all_connection_tests() to keep cli.py
      organized.
    • I debugged a couple of errors with @ghukill and he suggested that "logging.exception [may] not [be] needed for an understood exception like oracledb.exceptions.DatabaseError: ORA-12170: TNS:Connect timeout occurred" and posted that logging.error is sufficient for such cases (this requires ignoring Ruff rule TRY400).
  • I originally tried to store this method in carbon.app.helpers, but it wasn't possible due to a circular import.

• Added a .dockerignore file.

  • Copied the .dockerignore file from the Python CLI template repo!

How can a reviewer manually see the effects of these changes?

Review the following CloudWatch logs in Stage-Workloads.

1. Log showing clean exit from carbon.app.run_all_connection_tests and simplified error log for failed Data Warehouse connection test.
   

2. Log showing clean exit from carbon.app.run_all_connection_tests and simplified error log for failed Elements FTP connection test.
   

3. Log showing clean exit from carbon.app.run_all_connection_tests where all connection tests were successful.
   

4. Log showing successful Carbon run for HR Feed using carbon.config.Config
   

5. Log showing successful Carbon run for Articles Feed using carbon.config.Config
   

6. Screenshot showing XML files on Elements FTP server.
   

Includes new or updated dependencies?

NO

Developer

• README is updated to reflect all changes as needed
• All related Jira tickets are linked in commit message(s)

Code Reviewer

• The commit message is clear and follows our guidelines
  (not just this pull request message)
• There are appropriate tests covering any new functionality
• The documentation has been updated to reflect all changes or is not needed
• The changes have been verified
• New dependencies are appropriate or there were no changes

[jonavellecuerdo]

@ghukill @ehanson8 I just added the screenshot showing the successful upload of XML files to the Elements FTP server to
the PR description.

[ghukill]

I think it looks good! Nice work.

All my comments are questions / suggestions, so not formally requesting any changes and consider it approved. If you decide to implement any of these changes happy to re-review, but if you'd prefer to skip, okay with that too!

[ehanson8]

Looks good, a few questions. And I would recommend making the changes Graham suggested to streamline it. Great work!