opened
sebastianmacarescu
username_0
### Describe the bug

We use serverless-nextjs-plugin@2.5.1 with the following routes
`
- src: index
        path: /{slug}
        cors: true
        request:
          parameters:
            paths:
              slug: true
- src: index
        path: /{slug}/{page}
        cors: true
        request:
          parameters:
            paths:
              slug: true
              page: true
`

When trying to deploy we get:
`A sibling ({slug}) of this resource already has a variable path part -- only one is allowed (Service: AmazonApiGateway; Status Code: 400; Error Code: BadRequestException; Request ID: fecdce7a-751a-4c27-b16d-0ebc521b563a; Proxy: null)`

This happens because the next.js creates a custom page _error.js to handle all errors and the serverless-nextjs-plugin will create a catch-all proxy resource.

### Actual behavior

Got error: `A sibling ({slug}) of this resource already has a variable path part -- only one is allowed (Service: AmazonApiGateway; Status Code: 400; Error Code: BadRequestException; Request ID: fecdce7a-751a-4c27-b16d-0ebc521b563a; Proxy: null)`

If I deploy without above routes, manually delete the proxy resources from AWS console then deploy again it works.

### Expected behavior

We should have an option to not create that catch all proxy resource for the 404 pages.


### Steps to reproduce

Create an empty serverless project using serverless-nextjs-plugin@2.5.1. 
Configure the above routes and try to deploy

### Screenshots/Code/Logs
<!-- If applicable, add screenshots or a minimal repro (e.g code or configuration snippet or repository) to help explain your problem. If you have a runtime issue from Lambda/CloudFront, please check CloudWatch logs (note that Lambda@Edge logs are in a region closest to where you access CloudFront - NOT necessarily in `us-east-1` where the original Lambda is created) and post any logs or stacktraces if possible. See here for how to check logs: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-testing-debugging.html#lambda-edge-identifying-function-errors. If you have a build or deploy issue, please run with serverless --debug and post the logs. Please also post your serverless.yml. -->

### Versions
serverless-nextjs-plugin@2.5.1
serverless -v
Framework Core: 1.83.2
Plugin: 3.8.4
SDK: 2.3.2
Components: 2.34.9
serverless-nextjs-plugin ApiGatewayResourceProxyVar resource already has a variable path part
issue