feat:add new secret resolver to modules

[betinacosta]

Description

This PR implements the secret resolver into the sdk modules.

Type of Change

Please check the relevant option:

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Code refactoring
• Dependency update

How to Test

from sap_cloud_sdk import (
    adms,
    agent_memory,
    agentgateway,
    destination,
    dms,
    objectstore,
    print as print_service
)

from sap_cloud_sdk.core import (
    auditlog_ng,
    data_anonymization
)


def main() -> None:
    # Destination client
    destination_client = destination.create_client()
    print(f"Destination: {destination_client}")

    # ADMS client
    adms_client = adms.create_client()
    print(f"ADMS: {adms_client}")

    # Agent Gateway
    agent_gateway_client = agentgateway.create_client()
    print(f"Agent Gateway: {agent_gateway_client}")

    # Agent Memory
    agent_memory_client = agent_memory.create_client()
    print(f"Agent Memory: {agent_memory_client}")

    # DMS
    dms_client = dms.create_client()
    print(f"DMS: {dms_client}")

    # Object Store
    object_store_client = objectstore.create_client("default")
    print(f"Object Store: {object_store_client}")

    # Print Service
    print_client = print_service.create_client()
    print(f"Print: {print_client}")

    # Auditlog V3
    auditlog_client = auditlog_ng.create_client()
    print(f"Auditlog NG: {auditlog_client}")

    # Data Anonymization
    data_client = data_anonymization.create_client()
    print(f"Data Anonymization: {data_client}")

    

if __name__ == "__main__":
    main()

Checklist

Before submitting your PR, please review and check the following:

• I have read the Contributing Guidelines
• I have verified that my changes solve the issue
• I have added/updated automated tests to cover my changes
• All tests pass locally
• I have verified that my code follows the Code Guidelines
• I have updated documentation (if applicable)
• I have added type hints for all public APIs
• My code does not contain sensitive information (credentials, tokens, etc.)
• I have followed Conventional Commits for commit messages

Breaking Changes

If this PR introduces breaking changes, please describe:

• What breaks
• Migration path for users
• Alternative approaches considered

Additional Notes

Add any additional context, screenshots, or information that would help reviewers.

[NicoleMGomes]

This method shouldn't exist anymore

[NicoleMGomes]

Maybe instead of module, could it be service_name and instance_name?

[betinacosta]

I think service_name is better than module, but we already use instance in other situations, so I believe is better to keep it for consistence.

[NicoleMGomes]

Could be moved to resolve.

I'm just thinking this is not an EnvVarResolver generic, because it expects module and instance. Should we maybe have an SdkEnvVarResolver and an EnvVarResolver just with the variable name?

[betinacosta]

Makes sense. I will move _load_from_env to resolve. I will also rename to SdkEnvVarResolver. Regarding having a generic EnvVarResolver just with the variable name, do we have an use case for it?

[NicoleMGomes]

Same points here.

[NicoleMGomes]

I believe this configuration could be global or per module.

[NicoleMGomes]

Aren't we missing an BindingRootResolver indeed?

[betinacosta]

I renamed the BindingResolver to Resolver.

[NicoleMGomes]

Suggested change

	def get() -> Optional[SdkConfig]:

No need to duplicate sdk_config in the name since you are already have a class.

[NicoleMGomes]

Maybe we will need to have a generic list of args or an interface each resolver implement for ResolverParameters.

[betinacosta]

I'm not sure I follow. We already have a Protocol class called Resolver that the other resolvers implement.

[NicoleMGomes]

I believe this encapsulation is not needed. We could also have an central enum for module names if we need it, instead of magic strings. What do you think?

[betinacosta]

I like the idea of having an enum, but I would leave the encapsulation for better organization, so in the client we can do only: binding = config or load_secrets(instance)

[betinacosta]

I accept suggestions on where to have this enum.