[New Extension]: pglinter

### Is there an existing issue for this extension request?

- [x] I have searched for an existing issue, and could not find a duplicate request.

### Extension Name

pglinter

### Project Repository URL

https://github.com/pmpetit/pglinter

### Extension Website URL (Optional)

[pglinter](https://pglinter.readthedocs.io/en/stable/)

### Short Description

Linter for database design.
for example, create a table with:

- one pk on a column "id"
- then, create an index on it
- then add unicity constraint on it.
This will create some duplicated indexes.

other example:
- create a table order in a schema "orders"
- create an other order_details in an other schema "public" with a fk on orders.order
it is not strictly forbidden by pg, but recognize it will be quite tricky to maintain (refresh,dumps....)

pglinter is here to create a sarif report about those wrong design.

### Main LICENSE Link

https://github.com/pmpetit/pglinter/blob/main/LICENSE

### License Compliance

- [x] The extension's license (linked above) complies with the list of allowed licenses.

### Known Dependent Extensions

n/a

### Component Owner and Maintenance Commitment

- [x] I/My organization commit to becoming the Component Owner and maintaining the extension image in the future.

### Additional Notes (Optional)

_No response_

### GitHub Handles of Component Owners

pmpetit

### Code of Conduct

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

Beginne damit, den bestehenden Extension-Image-Workflow des Repositorys postgres-extensions-containers und die verlinkte pglinter-Dokumentation zu lesen. Vergleiche, wie andere PostgreSQL-Extensions paketiert werden, und ermittle anschließend, was für ein pglinter-Image erforderlich ist und wie es validiert werden sollte. Erledigt ist die Aufgabe, wenn die Extension konsistent paketiert ist und ihr Owner das Image warten kann.

Vom Indexierungsmodell aus dem Issue-Text verfasst.