Fix renaming exports bug

[hawkeye217]

Proposed change

When the name of an export had a slash in it, the api returned 404. This PR fixes the bug by moving the patch request to the body rather than the url.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code
• Documentation Update

Additional information

• This PR fixes or closes issue:
  fixes [Bug]: Renaming exports fails with 404 error when new name contains a slash #15765
  fixes [Bug]: Renaming exports fails with 404 error when new name contains a slash #15764
• This PR is related to issue:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• The code has been formatted using Ruff (ruff format frigate)

[netlify]

✅ Deploy Preview for frigate-docs ready!

Name	Link
🔨 Latest commit	270563b
🔍 Latest deploy log	https://app.netlify.com/sites/frigate-docs/deploys/67afc1e496f93600086b9620
😎 Deploy Preview	https://deploy-preview-16588--frigate-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.