added missing unit test for functions in dynamicconfig/config.go

[d-vignesh]

What changed?
add units tests for functions in dynamicconfig/config.go

Why?
Improve test coverage

How did you test it?
go test

Potential risks

Release notes

Documentation Changes

[codecov]

Codecov Report

Merging #5885 (804c43c) into master (3a0d600) will decrease coverage by 0.17%.
The diff coverage is n/a.

❗ Current head 804c43c differs from pull request most recent head 0b6a5b9. Consider uploading reports for the commit 0b6a5b9 to get more accurate results

Additional details and impacted files

see 16 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3a0d600...0b6a5b9. Read the comment docs.

[coveralls]

Pull Request Test Coverage Report for Build 018ebef5-a178-47ea-9bdd-1c168fff5d52

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 46 unchanged lines in 12 files lost coverage.
• Overall coverage increased (+0.02%) to 67.287%

---

Files with Coverage Reduction	New Missed Lines	%
service/matching/matcher.go	1	91.07%
common/task/parallel_task_processor.go	2	93.06%
common/peerprovider/ringpopprovider/config.go	2	81.58%
common/persistence/execution_manager.go	2	83.54%
service/frontend/api/handler.go	2	62.05%
service/history/task/transfer_active_task_executor.go	2	72.7%
common/persistence/statsComputer.go	2	97.14%
common/archiver/filestore/historyArchiver.go	4	80.95%
service/history/task/redispatcher.go	4	89.53%
service/history/execution/mutable_state_task_refresher.go	7	62.03%

Totals
Change from base Build 018ebee7-9c32-494e-9892-ea9da6f92a1a:	0.02%
Covered Lines:	98074
Relevant Lines:	145755

---

💛 - Coveralls

[davidporter-id-au]

In general kindly add to the description all changes, including the refactoring of the contstants file.

[abhishekj720]

and prefer to write table tests for same methods but different cases as a better testing standard.

[d-vignesh]

and prefer to write table tests for same methods but different cases as a better testing standard.

sure, followed this approach as the existing test cases where in this pattern, will follow the table test approach for new tests.