Refactor: Generalize Complexity Score Calculation for Multiple Providers

[GeneCodeSavvy]

This PR refactors the DNA complexity score calculation to be more extensible and support multiple providers beyond IDT. The changes include generalizing function names, updating docstrings to be provider-agnostic, and preparing the script for future modularity improvements.

NOTE: This PR introduces breaking changes.

BREAKING CHANGE

Previous json file format:

{
    "username": "hxrsh.09",
	"password": "xxxxxxxx",
	"ClientID": "harsh",
	"ClientSecret": "xxxxx-xxxx-xxxx-xxxx-xxxxxxxxx"
}

New json file format:

{
	"idt": {
		"username": "hxrsh.09",
		"password": "xxxxxxxx",
		"client_id": "harsh",
		"client_secret": "xxxxx-xxxx-xxxx-xxxx-xxxxxxxxx"
	}
}

The new format stores the credentials as { "provider_name": { "key": "value", ... } }. It also adheres to snake case for all keys.

[GeneCodeSavvy]

The test are passing on my system. The environment variables will have to be updated for CI / CD

[jakebeal]

Before I approve and we merge, can you please provide the exact update that will be needed to make it pass?

[GeneCodeSavvy]

We need to update the secrets for the CI / CD. The secret IDT_CREDENTIALS should now be just CREDENTIALS in the specified format.

For users, the credentials should also be stored in the specified format, in the test_secret_credentials.json file.

New json file format:

{
	"idt": {
		"username": "hxrsh.09",
		"password": "xxxxxxxx",
		"client_id": "harsh",
		"client_secret": "xxxxx-xxxx-xxxx-xxxx-xxxxxxxxx"
	}
}

The new format stores the credentials as { "provider_name": { "key": "value", ... } }. It also adheres to snake case for all keys.

[jakebeal]

I have updated the secrets, but the tests are currently failing because some of the references are still to the old credentials and not the updated credentials.

[GeneCodeSavvy]

The tests are currently failing due to a mismatch in word casing:
client_id is being saved as ClientId.

This update should resolve the issue.

[GeneCodeSavvy]

@jakebeal @Gonza10V solved all the merge conflicts, a review would be appreciated.