Connectors Debugger V2 to pass through all types of mapping problems

[andrewmcgivery]

Connectors Debugger V2 to pass through all types of mapping problems

Open questions....

1. Do I actually need all the clone and cloned that I currently have? Rust seems to think so but open to suggestions
2. What is the impact of some of this code at run time when debug is not enabled? Is it worth passing debug all over to avoid some of the mapping of errors to problems? (thinking no since it's pretty trivial code but open to opinions)

Relies on https://github.com/mdg-private/studio-ui/pull/12112 (that needs to be in prod before this change lands in a Router release!)

---

Checklist

Complete the checklist (and note appropriate exceptions) before the PR is marked ready-for-review.

• Changes are compatible¹
• Documentation² completed
• Performance impact assessed and acceptable
• Metrics and logs are added³ and documented
• Tests added and passing⁴
  • Unit Tests
  • Integration Tests
  • Manual Tests

Exceptions

Note any exceptions here

Notes

Footnotes

1. It may be appropriate to bring upcoming changes to the attention of other (impacted) groups. Please endeavour to do this before seeking PR approval. The mechanism for doing this will vary considerably, so use your judgement as to how and when to do this. ↩

2. Configuration is an important part of many changes. Where applicable please try to document configuration examples. ↩

3. A lot of (if not most) features benefit from built-in observability and debug-level logs. Please read this guidance on metrics best-practices. ↩

4. Tick whichever testing boxes are applicable. If you are adding Manual Tests, please document the manual testing (extensively) in the Exceptions. ↩

[github-actions]

@andrewmcgivery, please consider creating a changeset entry in /.changesets/. These instructions describe the process and tooling.

[svc-apollo-docs]

✅ Docs preview has no changes

The preview was not built because there were no changes.

Build ID: 06f03750bd7307154435c8d4