feat: implement remote configuration and logging level updates

[ckshitij]

Pull Request

Description:

• Addess issue-2226
• Added RemoteConfigurable and RemoteConfiguration interfaces for runtime configuration management.
• Introduced mock implementations for testing remote configuration behavior.
• Enhanced remote logger to support dynamic log level updates via remote configuration.
• Implemented HTTP-based remote configuration fetching and client registration.
• Added comprehensive tests for remote configuration and logger functionality.

Checklist:

• I have formatted my code using goimport and golangci-lint.
• All new code is covered by unit tests.
• This PR does not decrease the overall code coverage.
• I have reviewed the code comments and documentation for clarity.

[ckshitij]

@coolwednesday and @aryanmehrotra kindly review the PR.

[Umang01-hash]

• Consider renaming interfaces for better clarity: RemoteConfigurable → ConfigSubscriber and RemoteConfiguration → ConfigProvider

• All the newly added tests inside remotelogger_test.go have if conditions in the end like:

	if atomic.LoadInt32(&logger.changeCnt) != 0 {
		t.Errorf("expected no ChangeLevel when invalid key present")
	}

	if !foundErrorLog {
		t.Errorf("expected error log message for invalid JSON response, got logs: %v", logger.messages)
	}

	if client.lastConfig["logLevel"] != "DEBUG" {
		t.Errorf("expected logLevel=DEBUG, got %v", client.lastConfig["logLevel"])
	}

We should generally avoid all these if-else conditions inside test methods. Please refactor your tests too.

• Same if-else conditions inside test lies in file remote_config_test.go. Please refactor it also.

• It would be nicer if you can also attach a screenshot of the functionality working after your changes so other developers can easily review.

[Umang01-hash]

Error handling in fetchRemoteConfig() should return nil, err instead of empty map on error

[Umang01-hash]

@ckshitij Thank you for contributing to GoFr. I have left some review comments on your PR. Please address them and we will review it again after all comments are resolved.

[Umang01-hash]

@ckshitij Are you still working on this PR? If yes, let's resolve the review comments quickly so we can further review your PR.

[ckshitij]

@ckshitij Are you still working on this PR? If yes, let's resolve the review comments quickly so we can further review your PR.

@Umang01-hash Yes I’m still working on the same, got busy with something , will try to address the comments by this weekend.