test: add k6 credential definition performance scenario

[antonbaliasnikov]

Overview

Adds K6 performance scenario to measure credential definition endpoint

Checklist

My PR contains...

• No code changes (changes to documentation, CI, metadata, etc.)
• Bug fixes (non-breaking change which fixes an issue)
• Improvements (misc. changes to existing features)
• Features (non-breaking change which adds functionality)

My changes...

• are breaking changes
• are not breaking changes
• If yes to above: I have updated the documentation accordingly

Documentation

• My changes do not require a change to the project documentation
• My changes require a change to the project documentation
• If yes to above: I have updated the documentation accordingly

Tests

• My changes can not or do not need to be tested
• My changes can and should be tested by unit and/or integration tests
• If yes to above: I have added tests to cover my changes
• If yes to above: I have taken care to cover edge cases in my tests

[github-actions]

Integration Test Results

11 files  ±0  11 suites  ±0   2s ⏱️ ±0s
24 tests ±0  24 ✔️ ±0  0 💤 ±0  0 ❌ ±0 
25 runs  ±0  25 ✔️ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit ef023f5. ± Comparison against base commit 4af753a.

♻️ This comment has been updated with latest results.

[github-actions]

Atala PRISM Test Results

  85 files  ±0    85 suites  ±0   21m 28s ⏱️ +11s
712 tests ±0  704 ✔️ ±0  8 💤 ±0  0 ❌ ±0 
718 runs  ±0  710 ✔️ ±0  8 💤 ±0  0 ❌ ±0 

Results for commit ef023f5. ± Comparison against base commit 4af753a.

♻️ This comment has been updated with latest results.

[antonbaliasnikov]

Linter failure is OK, we can't fix it.

[ghost]

I've picked up bringing this work into the current release in this new PR #865