(#3062) X-Ray Support for NextJs Applications

### Is this related to a new or existing framework?

Next.js

### Is this related to a new or existing API?

Analytics

### Is this related to another service?

Linked to aws-amplify/amplify-js#3062
Lambda, DynamoDB, EC2, ...

### Describe the feature you'd like to request

We'd like to have more visibility and observability for our Next.js applications deployed with AWS Amplify.

At the moment, it feels like a black box as we don't have a clear understanding of the resources created by CloudFormation and the interaction between them (e.g., Lambda for Next.js APIs, Next server, and other interactions).

We're particularly interested in middleware interaction with the server, triggered Lambdas, external API calls, interaction with DynamoDB, and similar AWS services...

### Describe the solution you'd like

We would like AWS Amplify to support AWS X-Ray or a similar service for Next.js applications, allowing us to trace requests, monitor application performance, and understand the interaction between different components of our application. The ability to see which CloudFormation resources are being created by Amplify would also be beneficial.

### Describe alternatives you've considered

We've considered manually configuring our services with AWS CloudFormation and using AWS X-Ray ourselves, but this seems not possible at the moment.

### Additional context

Having better observability in Amplify for Next.js applications would make it much easier for us to debug issues, optimize performance, and have a better understanding of our application's behavior. We believe that this would be a valuable feature for many AWS Amplify users.

### Is this something that you'd be interested in working on?

- [X] 👋 I may be able to implement this feature request
- [X] ⚠️ This feature might incur a breaking change

The issue names no files, tests, or implementation entry points. Start by reviewing the existing Next.js hosting integration and how Amplify provisions CloudFormation resources, then determine the scope for tracing middleware, triggered Lambdas, external API calls, and AWS service interactions; done means supported X-Ray visibility for these interactions.

Written by the indexing model from the issue text.