Fix spector mess

[timotheeguerin]

1. Get rid of axios and form-data and use fetch (had to change 2 bad test getModel and headModel which passed data in the body to pass it in query instead in visibility spec)
2. Update all spec to use the same way to define request and response body with better type support
3. Pretty sure the validation wasn't working correctly before, caught some issues
4. Reuse the validation error and print them better inline to see what was not send/received correctly
5. Remove legacy mock api interface
   Disabled the nextLink server test response check as we ened a better way to define that. Thinking something like vitest

response {
  nextLink: expect.toEndWith(...)
} 

Improvement to the output

errors

[github-actions]

All changed packages have been documented.

• ✅ @typespec/http-specs
• ✅ @typespec/spec-api
• ✅ @typespec/spector

Show changes

@typespec/http-specs - fix ✏️

Fix specs to handle body correctly with new spector change

@typespec/spector - feature ✏️

Make handling of request body and response body consistent

@typespec/spec-api - feature ✏️

Make handling of request body and response body consistent

[azure-sdk]

You can try these changes here

🛝 Playground	🌐 Website	🛝 VSCode Extension

[chrisradek]

Overall looks like an improvement to me!