feat: Remove XSUAA binding dependency from destination retrieval flow
Closes SAP/cloud-sdk-backlog#1274.
Changes have been tested manually in an E2E test, I used both an user IAS JWT and user XSUAA JWT to test destination(s) retrievals.
Working E2E test run: https://github.tools.sap/cloudsdk/sdk-js/actions/runs/15330543 with a canary release of these changes.
@deekshas8 @jjtang1985 I also removed the JWT verification step while trying to fetch a destination(as it is relying on XSUAA binding). This is a behaviour change,please let me know if the change is okay and approved by you.
Before merging this, it would be nice if we create an E2E test that fails on the current release and passes on this PR / canary.
Before merging this, it would be nice if we create an E2E test that fails on the current release and passes on this PR / canary.
Yes, as discussed, already working on the E2E test. But, I don't think we need to wait for the E2E test to merge this as I already tested the changed manually in an E2E test.