CLOUDP-278958: trasformation test

[wtrocki]

Proposed changes

Jira ticket: CLOUDP-278958

Descriptions

Adding test to the customization mechanism we use to track possible regressions and issues when postman tooling is updated.

Impact

Releases will require tests to pass. I intentionally made test simple to cover happy path/critical changes only.

Reason

Transformation engine is currently done as set of bash jq commands that are tricky to test and validate.
Transformation files are not committed to the repository and visible during PRs.
We release postman automatically (postman does validation for correctness on backend) but it does not validate our customizations.

Testing

• Run locally:

▶ make transform_collection_test
./scripts/transform-for-api-test.sh
~/Projects/sandbox/openapi/tools/postman/tmp ~/Projects/sandbox/openapi/tools/postman
Test Passed: Query params disabled successfully.
Test Passed: _postman_id removed successfully.
Test Passed: The first item in the variable array has key set to "baseUrl" and has a value property.

• CI/CD will be tested after merge.

Future considerations

To fully streamline the experience for postman, we would need to move all the org and group variables to the global level for user convenience. I initially tried to do that, but bash approach does show it's limit:

• It is difficult to test jq commands which do not fail if entries are missing
• long execution time - added loop in bash took 610 seconds to run transformation.

In the long run we should look to see if we can migrate transformation engine into scripting language like python, js etc.