Added check for last modified time to settings CLI

[carlosfelix2]

This PR adds the option to update the settings only if they were updated.

Example run of the CLI:
./prime multiple-settings set -i ./settings/organizations.yml --check-last-modified

Test Steps:

1. Build and start your RS container.
2. Restart your RS container.
3. Verify that the RS logs show the settings were not updated. The log message looks like this: No new updates found for settings.

Changes

• add the option to update the settings only if they were updated

Checklist

Testing

• Tested locally?
• Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
• (For Changes to /frontend-react/...) Ran npm run lint:write?
• Added tests?

Process

• Are there licensing issues with any new dependencies introduced?
• Includes a summary of what a code reviewer should test/verify?
• Updated the release notes?
• Database changes are submitted as a separate PR?
• DevOps team has been notified if PR requires ops support?

Fixes

• Settings CLI should load settings for local runs only if they have been updated #3399

To Be Done

Specific Security-related subjects a reviewer should pay specific attention to

• Does this PR introduce new endpoints?
  • new endpoint A
  • new endpoint B
• Does this PR include changes in authentication and/or authorization of existing endpoints?
• Does this change introduce new dependencies that need vetting?
• Does this change require changes to our infrastructure?
• Does logging contain sensitive data?
• Does this PR include or remove any sensitive information itself?

If you answered 'yes' to any of the questions above, conduct a detailed Review that addresses at least:

• What are the potential security threats and mitigations? Please list the STRIDE threats and how they are mitigated
  • Spoofing (faking authenticity)
    • Threat T, which could be achieved by A, is mitigated by M
  • Tampering (influence or sabotage the integrity of information, data, or system)
  • Repudiation (the ability to dispute the origin or originator of an action)
  • Information disclosure (data made available to entities who should not have it)
  • Denial of service (make a resource unavailable)
  • Elevation of Privilege (reduce restrictions that apply or gain privileges one should not have)
• Have you ensured logging does not contain sensitive data?
• Have you received any additional approvals needed for this change?

Pull reviewers stats

Stats for the last 30 days:

	User	Total reviews	Median time to review	Total comments
	MauriceReeves-usds	32	15h	11
	cwinters-usds	31	1h 50m	20
	kevinhaube	22	28m	10
	sean-usds	19	1h 22m	7
	carlosfelix2	18	10h 17m	55
	jimduff-usds	17	1d 2h 18m	11
	RickHawesUSDS	15	4h 12m	6
	whytheplatypus	10	17h 22m	20
	clediggins-usds	10	2h 51m	24
	TomNUSDS	9	40m	2
	jbiskie	5	1h 26m	1
	jorg3lopez	3	1d 8h 45m	0
	brick-green-agile6	3	15m	2
	JosiahSiegel	2	2d 13h 27m	4
	ahay-agile6	2	1d 9h 28m	0
	MikeC-A6	1	7h 7m	3
	rhood23699	1	14h 10m	0
	sethdarragile6	1	2h 17m	0

[github-actions]

Unit Test Results

  41 files  ±0    41 suites  ±0   33s ⏱️ -1s
309 tests ±0  305 ✔️ ±0  4 💤 ±0  0 ❌ ±0 

Results for commit 1a219e3. ± Comparison against base commit 42bd1ae.

♻️ This comment has been updated with latest results.

[github-actions]

Integration Test Results

11 files  11 suites   1m 55s ⏱️
83 tests 83 ✔️ 0 💤 0 ❌

Results for commit 1a219e3.

♻️ This comment has been updated with latest results.

[jimduff-usds]

lgtm.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication