[Enhancement]: The rest endpoint is in the background odata. But it doesn't present an OData MetadataEndpoint

### What happened?

The `/rest/...` of the genereated API contains at the end technically an ODATA endpoint. But the problem is for many API tools is, that the generated part doesn't make the `$metadata` endpoint accessible. This endpoint is for example used in PowerBi to be connected to an OData API and get the schema and all valid endpoints from it.

So my expactation would be that I could call:

`rest/$metadata` and get the XML schema of the OData feed back.

Currently I get:

```json
{"error":{"code":"EntityNotFound","message":"Invalid Entity path: $metadata.","status":404}}
```

### Version

Azure Static Web Apps CLI (1.1.3)

### What database are you using?

Azure SQL

### What hosting model are you using?

Static Web Apps (SWA)

### Which API approach are you accessing DAB through?

REST

### Relevant log output

_No response_

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

Inizia tracciando il modo in cui l’API REST generata gestisce il punto di ingresso `/rest/...` e il motivo per cui `/rest/$metadata` restituisce `EntityNotFound`. Verifica il comportamento rispetto all’Azure SQL REST API, quindi verifica che l’endpoint restituisca lo schema XML OData ed esponga gli endpoint dei feed validi attesi da strumenti come Power BI.

Scritto dal modello di indicizzazione a partire dal testo della issue.