test: refactor integration tests - assertions, client models

[antonbaliasnikov]

Overview

Refactoring of integration tests:

• Use of client models
• Remove unused code and wrong assertions
• Use of Ensure
• Use of atala automation library
• Clean ups and fixes

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   3s ⏱️ ±0s
23 tests  -   2  23 ✔️  -   2  0 💤 ±0  0 ❌ ±0 
24 runs   - 13  24 ✔️  - 13  0 💤 ±0  0 ❌ ±0 

Results for commit 99a1ae6. ± Comparison against base commit e790efe.

This pull request removes 2 tests.

PRISM DID creation fails when required request fields are missing
PRISM DID creation fails with wrong formatted fields

♻️ This comment has been updated with latest results.

[github-actions]

Atala PRISM Test Results

  79 files  ±0    79 suites  ±0   15m 18s ⏱️ -36s
680 tests ±0  669 ✔️ ±0  11 💤 ±0  0 ❌ ±0 
686 runs  ±0  675 ✔️ ±0  11 💤 ±0  0 ❌ ±0 

Results for commit 99a1ae6. ± Comparison against base commit e790efe.

♻️ This comment has been updated with latest results.