Chalice API Gateway endpoint vs local - paths are different

When deploying our chalice app, we will get an API Gateway url of the form
`https:////`
e.g.
`https://xxxxxxxxxx.execute-api.us-east-1.amazonaws.com/prod/`

when testing locally using `chalice local` how do we simulate the `` in the path?

Finding it difficult to do some local sanity testing because the paths end up all different

The issue names no files or tests. Start by running `chalice local` and comparing its route paths with the deployed API Gateway stage prefix; define the desired local behavior and verify it against both local requests and the deployed URL structure.

Written by the indexing model from the issue text.