Vector Tile Server

**As a** *FBA* **I want** *zippy, up to date, and relevant fire zone outlines visible on map* **So That** *I have context for the area I'm looking at*

**Additional Context**
- Fire zones raster tile sets sucks (zoom level issues)
- Fire zone raw vector data sucks (too big!)
- https://github.com/CrunchyData/pg_tileserv
- Engaging with databc re. vector tile server
- We have a server running in dev, it's not production ready though.
- pg_tileserv need a proxy server in front of it to cache common requests.

**Acceptance Criteria**
- [x] production ready pg_tileserver instance deployed in production namespace
- [x] Fire zone data populated into database
- [ ] Fire zone data updates periodically to stay in sync
- [x] Switch zone to new endpoint

**Definition of Done**
- [ ] Ready to Demo in Sprint Review
- [ ] Does what I have made have appropriate test coverage?
- [ ] Documentation and/or scientific documentation exists and can be found
- [ ] Peer Reviewed by 2 people on the team
- [ ] Manual testing of all PRs in Dev and Prod
- [ ] Merged

Inspect the current production pg_tileserv deployment and the fire-zone data in the database, then determine how updates are currently handled. Done means the fire-zone data updates periodically to stay in sync, with appropriate tests, documentation, and manual validation in Dev and Prod.

Written by the indexing model from the issue text.