Remove the test checking whether the JSON Schema default config matched the old default config

[aloisklink]

📑 Summary

In PR #4112, we drastically changed how the default MermaidConfig was defined, from a normal TypeScript literal, to a JSON Schema in a YAML file using a custom Vite plugin.

Because of this change, we added a temporary test (see 063cb12) to ensure that the JSON Schema way of defining the default config was exactly the same as the old default config.

Now that PR #4112 has been merged, we can revert 063cb12 to remove this temporary test.

See also discussion in #4112 (comment).

📏 Design Decisions

This test actually broke when merging PR #4112 due to a bad merge commit. I've fixed the test in 2b53e02, so that we have a working copy of the test in the git history, in case anybody wants to git checkout 2b53e021537597819b87edfc4e06d0d292f7477c and view the it/use it for their own PRs.

📋 Tasks

Make sure you

• 📖 have read the contribution guidelines
• 💻 have added unit/e2e tests (if appropriate)
  • I've removed a unit test instead :)
• 📓 have added documentation (if appropriate)
• 🔖 targeted develop branch

[codecov]

Codecov Report

Merging #4610 (8167f8c) into develop (194ef20) will decrease coverage by 0.03%.
The diff coverage is n/a.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #4610      +/-   ##
===========================================
- Coverage    76.99%   76.96%   -0.03%     
===========================================
  Files          143      143              
  Lines        14455    14455              
  Branches       516      516              
===========================================
- Hits         11130    11126       -4     
- Misses        3220     3225       +5     
+ Partials       105      104       -1     

Flag	Coverage Δ
e2e	83.91% <ø> (-0.04%)	⬇️
unit	45.28% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 1 file with indirect coverage changes