feat: add mkcalendar & Report to body methods in next

[keyservlad]

Checklist

For context see #5439

• run npm run test and npm run benchmark
• tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows the Developer's Certification of Origin
  and the Code of conduct

[gurgunday]

This is normally in alphabetical order

Also just realized 'MKCOL' should be above 'MOVE' for the same reason, would be great if you could move it too

[gurgunday]

The rest of the changes we can pull from main I think, but maybe we should add their shorthands here as well

Like this: #4409

[keyservlad]

I merged main and added the route shorthand methods.
Still getting the route-shorthand test failing tho ahah ;D

Edit: Fixed it

[gurgunday]

yeah looks great, just one issue, because we use squash merge, I think we should merge main to next first, and merge this after that, otherwise all these merge changes will end up being conflicts

edit: or maybe not

[gurgunday]

lgtm

Oops, wrong place 😄

So we had to manually merge to next and had to include the changes of this PR, thanks anyway for the PR!

#5444 (review)

[keyservlad]

@gurgunday Thank you guys very much for your work. I noticed you didn't include the route shorthand changes for the new methods. If you ever want to implement them, you can find the changes needed in this PR.

Here are the files to change :
docs/Reference/Routes.md

test/types/route.test-d.ts
instance.d.ts

[gurgunday]

Good spot, the shorthands were added, but you are right that the types weren't, opening the PR again to not forget

[keyservlad]

I will try to rebase and get rid of the commits that come from the merge if that's ok with you

[gurgunday]

Yeah but I’d say let’s wait for the merge to main of v5 first, like @jsumners said, or maybe he’ll add it manually

[gurgunday]

Again, sorry for the trouble, can you open the type PR again? It can be a new PR to make things easier, and it should target main now