Feature/config injection

[tznind]

Proposed Changes

• Removes the requirement to have environment variables (they are still respected if present though).
• Refactoring to improve extensibility of config files secrets

Types of changes

What types of changes does your code introduce? Tick all that apply.

• Bugfix (non-breaking change which fixes an issue)
• New Feature (non-breaking change which adds functionality)
• Breaking Change (fix or feature that would cause existing functionality to not work as expected)
• Documentation-Only Update (if none of the other choices apply)
  • In this case, ensure that the message of the head commit from the source branch is prefixed with [skip ci]

Checklist

By opening this PR, I confirm that I have:

• Reviewed the contributing guidelines for this repository
• Ensured that the PR branch is in sync with the target branch (i.e. it is automatically merge-able)
• Updated any relevant API documentation
• Created or updated any tests if relevant
• Accurately updated the CHANGELOG
  • NOTE: This must include any changes to any of the following files: default.yaml, any of the RabbitMQ server configurations, GlobalOptions.cs
• Listed myself in the CONTRIBUTORS file 🚀
• Requested a review by one of the repository maintainers

Issues

If relevant, tag any issues that are expected to be resolved with this PR. E.g.:

\fixes #382

[tznind]

Thanks for reviewing the changes @rkm. I see you madeSetMongoPassword and GlobalOptions.ForAll static, was that deliberate? They are not accessed from a static context.

[rkm]

I don't mind either way to be honest, it was suggested by resharper though and looks to be valid since they don't access instance variables at all?

[tznind]

I don't mind either way to be honest, it was suggested by resharper though and looks to be valid since they don't access instance variables at all?

Ah ok, I think I will undo it. Not a fan of making stuff static without a good reason. It often gets in the way later on.