Allow env variable substitution in CLI client properties

[VillePekka]

Testing the functionality on Linux:

1. In mirth-cli-config.properties file, define for example password as password=${env:OIE_PASSWORD}
2. Define the environment variable in commandline export OIE_PASSWORD=<password>
3. Run cli client ~/engine/server/setup$ java -jar mirth-cli-launcher.jar -c ../../command/conf/mirth-cli-config.properties

[Copilot]

Pull request overview

This pull request adds environment variable substitution support to the CLI client properties file by replacing the standard Java Properties class with Apache Commons Configuration2's Configuration interface. This allows users to specify property values like password=${env:OIE_PASSWORD} in the configuration file, which will be resolved from environment variables at runtime.

Changes:

• Replaced Properties with Apache Commons Configuration2's Configuration for loading CLI configuration
• Added new imports for Configuration2 classes
• Modified configuration loading logic to use FileBasedConfigurationBuilder instead of direct file reading

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[VillePekka]

Plan is to next test different scenarios with both correct and incorrect credentials:
*** Login with user and password given on the command line
*** Login with config file
**** with credentials directly in the file
**** with credentials as environment variables
**** with mistyped environment variable

[tonygermano]

I did the following:

• squashed all commits
• fixed whitespace issues
• rebased onto main
• removed some unnecessary imports
• reverted copilot suggestion and initialized config to empty BaseConfiguration

I tested all of your scenarios mentioned in #242 (comment)

I also tested with no config file

• no command line arguments (shows help)
• setting -a -u and -p on the command line (logs in if everything is valid)
• setting -a and -u, but not -p (shows help)

[mgaffigan]

Did not test, but the changes look good.

[VillePekka]

I did the following:

* squashed all commits
* fixed whitespace issues
* rebased onto main
* removed some unnecessary imports
* reverted copilot suggestion and initialized config to empty BaseConfiguration

I tested all of your scenarios mentioned in #242 (comment)

I also tested with no config file

* no command line arguments (shows help)
* setting -a -u and -p on the command line (logs in if everything is valid)
* setting -a and -u, but not -p (shows help)

Thank you @tonygermano !
Could you explain how you fixed whitespace issues, or give some pointer how to fix them in the future?
I tried with unix2dos command but that didn't seem to fix the issue.