Next.js edge middleware support

### Before opening, please confirm:

- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting questions](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have removed any sensitive information from my code snippets and submission.

### App Id

d3akk1nl18rszx

### AWS Region

us-east-1

### Amplify Hosting feature

Not Applicable

### Question

My question is whether AWS Amplify currently supports Next.js edge middleware?
Since middleware plays a crucial role in handling requests before they reach the application's paths. To ensure optimal performance, it is imperative that this middleware is deployed on the edge, effectively reducing Time To First Byte (TTFB) impacts. This is crucial to avoid any potential delays caused by cold boots on the middleware.

Per documentations (Unsupported features):
Edge API Routes (Edge middleware is not supported)

But the edge middleware is very crucial for optimal performance.

Start with the Amplify Hosting documentation section on unsupported features and investigate the current deployment path for Next.js edge middleware. The issue names no source files or tests, so confirm the supported behavior and identify the documentation or hosting changes needed before defining done.

Written by the indexing model from the issue text.