Unifying the Request Signing Strategy

[noCharger]

In #303, we introduced a separate signing strategy for accessing metadata. Moving forward, we may consider implementing a more flexible approach. For instance, while SigV4a could serve as the default, users might have the option to specify either a role-based or policy-based signing strategy via Spark submit parameters.