refactor(backend): move the routers for postmark to not the v2 folder

[ntindle]

One of the pull request review notes from when these were first made is that they don't belong in the v2 folder. This pr fixes where they are.

Changes 🏗️

• Moves from v2 to routers for the postmark tooling

Checklist 📋

For code changes:

• I have clearly listed my changes in the PR description
• I have made a test plan
• I have tested my changes according to the test plan:
  • Check that linting and tests pass

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Tag Change The router tags have been changed from ["v2", "email"] to ["v1", "email"]. Verify this change is intentional and aligns with the API versioning strategy. tags=["v1", "email"], prefix="/api/email",

[deepsource-io]

Here's the code health analysis summary for commits 942ac0b..c5ce535. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success		View Check ↗
Python	✅ Success	❗ 80 occurences introduced 🎯 34 occurences resolved	View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[github-actions]

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

[github-actions]

Conflicts have been resolved! 🎉 A maintainer will review the pull request shortly.

[Bentlybro]

Looks good to me!

The base branch was changed.

[github-actions]

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

[AutoGPT-Agent]

While this PR appears to be a relatively simple move of files from one directory to another to fix code organization, there are some issues:

1. The PR title and scope match correctly
2. A user_id check is not applicable here as this is just moving files and updating imports
3. The test plan could be more comprehensive to ensure routes still work after the move
4. The PR template is mostly filled out correctly, though some sections could be removed as they aren't applicable (config changes)
5. The changes appear to be 100% in scope with no extra modifications