Releasing `v0.15.0`

[CommanderStorm]

Hi @nyurik @sharkAndshark
Quick check in if the current state would be a good place to do a release or if something has to be finished first (we have not done one in some time => lets not leave too many features "in limbo").

I went through the commits and came up with the following. What do you think? ^^
The list is ordered somewhat by how important I think they are => please feel free to reorder

# martin

## Features

* Add basic `cog` (Cloud Optimized GeoTIFF)  support by @sharkAndshark in https://github.com/maplibre/martin/pull/1590
* Add `sdf` sprites which can be colored by the map dynamically via additional apis by @CommanderStorm in https://github.com/maplibre/martin/pull/1492
* Add support for `geography` columns by @rshk in https://github.com/maplibre/martin/pull/1627
* Add basic web UI (not currently usable) d by @paigewilliams in https://github.com/maplibre/martin/pull/1395
* Add `HEALTHCHECK` instruction to the Dockerfile by @caspg in https://github.com/maplibre/martin/pull/1397
* Use comment on view to generate TileJson by @sharkAndshark in https://github.com/maplibre/martin/pull/1507
* Add a postgres version check to not run on versions of postgis that we don't support by @CommanderStorm in https://github.com/maplibre/martin/pull/1427
* Use layer id if it is provided by @sharkAndshark in https://github.com/maplibre/martin/pull/1501
* Added validate function to PgConfig and invoked it in finalize and pool initialization by @Saru2003 in https://github.com/maplibre/martin/pull/1546

## Refactorings and enhancements
* Add port fwd test by @nyurik in https://github.com/maplibre/martin/pull/1411
* Minor lints by @nyurik in https://github.com/maplibre/martin/pull/1412
* Update tests, connection limit by @nyurik in https://github.com/maplibre/martin/pull/1530
* Cleanup `test.sh`, fix json rounding issue by @nyurik in https://github.com/maplibre/martin/pull/1543
* unified the types to be based on `TileInfoSource` by @CommanderStorm in https://github.com/maplibre/martin/pull/1611
* Group dependency updates for GitHub Actions and Cargo by @nakul-py in https://github.com/maplibre/martin/pull/1623
* Temporary disable macos-13 testcase by @CommanderStorm in https://github.com/maplibre/martin/pull/1626

# Documentation

* Fix curl url for linux mbtiles demo by @tbo47 in https://github.com/maplibre/martin/pull/1387
* Create run-with-apache.md by @agenceKanvas in https://github.com/maplibre/martin/pull/1394
* Document the `--base-path` option better by @CommanderStorm in https://github.com/maplibre/martin/pull/1420
* Better differentiation between `image_id` and `sprite_id`s by @CommanderStorm in https://github.com/maplibre/martin/pull/1491
* Typo fixes by @jleedev in https://github.com/maplibre/martin/pull/1388 and @CommanderStorm in https://github.com/maplibre/martin/pull/1597
* Fixed the security policy not being recognised by github and add citations by @CommanderStorm in https://github.com/maplibre/martin/pull/1600

## New Contributors
* @tbo47 made their first contribution in https://github.com/maplibre/martin/pull/1387
* @agenceKanvas made their first contribution in https://github.com/maplibre/martin/pull/1394
* @caspg made their first contribution in https://github.com/maplibre/martin/pull/1397
* @paigewilliams made their first contribution in https://github.com/maplibre/martin/pull/1395
* @CommanderStorm made their first contribution in https://github.com/maplibre/martin/pull/1420
* @Saru2003 made their first contribution in https://github.com/maplibre/martin/pull/1546
* @nakul-py made their first contribution in https://github.com/maplibre/martin/pull/1623
* @rshk made their first contribution in https://github.com/maplibre/martin/pull/1627

**Full Changelog**: https://github.com/maplibre/martin/compare/v0.14.2...v0.15.0

[nyurik]

you read my mind :)

Lets do one last bump of dependencies (using cargo update), and publish. @CommanderStorm want to do the honors?

[nyurik]

P.S. note that some updates might break, so we may want to keep back on those. Lets bump everything that's easy to bump

[sharkAndshark]

We really should do a new release

[nyurik]

my only concern is that we no longer have a stable ci :(

[nyurik]

@CommanderStorm we don't have to wait for CI stabilization to release, but that also means we may need to comment out the failing tests in the meantime

[lastzero]

Besides being able to ship additional features, a new release (at least) every few months is also good for security reasons, as it ensures that the binaries are built with the latest compiler (which may include fixes/improvements) and that the Docker container also includes the latest security patches.