fix: avoid name and operationId conflict when creating oas client

[patlo-iog]

Description:

This fix some issues when generating OAS client as it fails some validation. New client release is required for new oid4vci test scenarios.

Alternatives Considered (optional):

Link to existing ADR (Architecture Decision Record), if any. If relevant, describe other approaches explored and the selected approach. Documenting why the methods were not selected will create a knowledge base for future reference, helping prevent others from revisiting less optimal ideas.

Checklist:

• [ ] My PR follows the contribution guidelines of this project
• [ ] My PR is free of third-party dependencies that don't comply with the Allowlist
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] I have checked the PR title to follow the conventional commit specification

[github-actions[bot]]

Integration Test Results

16 files  ±0  16 suites  ±0   2s :stopwatch: ±0s 34 tests ±0  34 :white_check_mark: ±0  0 :zzz: ±0  0 :x: ±0  59 runs  ±0  59 :white_check_mark: ±0  0 :zzz: ±0  0 :x: ±0 

Results for commit b88f42e1. ± Comparison against base commit f0905545.

[github-actions[bot]]

Unit Test Results

 96 files  ±0   96 suites  ±0   21m 35s :stopwatch: - 1m 40s 826 tests ±0  818 :white_check_mark: ±0  8 :zzz: ±0  0 :x: ±0  833 runs  ±0  825 :white_check_mark: ±0  8 :zzz: ±0  0 :x: ±0 

Results for commit b88f42e1. ± Comparison against base commit f0905545.