feat(settings): settings path can be set through command-line

[manusa]

Relates to #363

[Copilot]

Pull Request Overview

This PR adds the ability to specify a custom settings file path through a command-line argument --settings-path. This enables users to use multiple profiles or custom configurations by pointing to different settings files.

• Added setSettingsPath function to dynamically update the settings file location
• Implemented command-line argument parsing to accept --settings-path parameter
• Updated test utilities to use the new settings path API instead of direct path manipulation

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
src/settings/index.js	Added setSettingsPath function and exported it; removed internal paths export
src/settings/tests/index.test.js	Added comprehensive tests for the new setSettingsPath functionality
src/index.js	Added command-line argument parsing to support --settings-path option
src/tests/settings.js	Updated test setup to use setSettingsPath instead of direct path manipulation

[Copilot]

The command-line argument parsing lacks validation. If the argument after --settings-path is another flag (starts with '--'), it will be incorrectly treated as a file path. Consider adding validation to ensure the argument is a valid path.

Suggested change

	if (settingsPathIndex !== -1 && args[settingsPathIndex + 1]) {
	if (
	settingsPathIndex !== -1 &&
	args[settingsPathIndex + 1] &&
	!args[settingsPathIndex + 1].startsWith('--')
	) {

[Copilot]

Pull Request Overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated no new comments.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
92.1% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud