Migrate cquisitor features to Mesh Devtools website (M1)

[jinglescode]

• Migrate cquisitor features to repo, web
  • select the most used features
  • it must be useful for TW and Eugene. show transaction schema in a easy to read way, good for new developers useful for teaching, and useful for advance users for most common tasks
• Update the dependency which make cquisitor feature complete and chang compatible
• a UI for new cquisitor
  • UI that accepts common format that developers will use to represent transaction
  • forward thinking: to make space for validation, identify errors and provide explanations and hints
  • forward thinking: URL should accept params that Mesh tx builder can provide links to analyze errors

[HinsonSIDAN]

On top of direct migration from current Cquisitor web, suggest to add below features / slight refinement.

1. Core component should be Transaction - as most dev use cquisitor for inspecting transaction. Sub-features:
   • Visualization of input outputs
   • Show everything, decoding all stuff, including datum and address etc
   • Inspect everything (like current cquisitor, can choose network and click to cardanoscan for details)
   • Allow evaluate and show phase 1 & 2 details
   • Good to have / extra - Copy as code (e.g. output datum type, can copy as mesh typescript code)

2. Frontend caching for favourite parsers - up to 5

3. Merging Mesh Utilities with Mesh Cquisitor
   For each mesh utilities function, there are 2 options - first run as normal cquistor operation, second is the API if it is hosted

For bigger picture, some API services in the future might require certain "checks" before using, like delegating to certain drep certs, containing contribution history to mesh etc