Secrets Manager Client: Raise error when OpenBao API response includes warnings

To ensure that we catch unexpected failures in during development and testing, we should raise an error when the OpenBao API response includes a warning. Currently, this is ignored by the secrets manager client and so some test failures can be hard to debug.

Development plan

Warning Categorization

1. Audit OpenBao documentation for all possible warning types
2. Create two lists:
   • Warnings safe to ignore (log only)
   • Warnings requiring error/blocking
3. Implement warning detection in OpenBao response handler
   • Apply categorization logic step 2
   • We can check if there is a warning in Openbao response Here by body["warnings"]
   • For safe warnings: log and continue
   • For critical warnings: raise appropriate error with clear message
   • Add tests for each warning scenario

Validation steps

1. Review warning categorization list for completeness
2. Trigger each warning type in test environment
3. Verify safe warnings are logged but don't block operations
4. Confirm critical warnings display error and prevent action
5. Check logs contain all expected warning details