Allow servers to start with no background services

[cicdw]

This PR enhances the prefect server start command to allow for:

prefect server start --no-services

Which starts only the webserver and the "services" necessary for event processing (which aren't actual loop services).

I realized that prefect server start creates a single connection pool to the database that is shared across both the webserver and all running loop services; this seems problematic to me in high scale / high traffic situations - those connection pools have fundamentally different properties (timeout configuration, pool configuration, etc.).

The eventual idea is to recommend pairing this new flag with a new CLI command prefect services start that starts only the background loop services. This allows users to easily decouple these two components of the backend, scale them independently, etc. and in the short term will allow us to see if there are differences in connection statistics between services and the webserver through the new PREFECT_SERVER_DATABASE_CONNECTION_APP_NAME setting.

[codspeed-hq]

CodSpeed Performance Report

Merging #16693 will not alter performance

_{Comparing no-services (1e35e6e) with main (d069600)}

Summary

✅ 2 untouched benchmarks

[cicdw]

I'm realizing that re-using the ephemeral flag means the UI will never be served properly; I'm not opposed to merging this as-is for debugging purposes, but open to push back on that - either way I'll begin thinking about how to refactor this implementation so that the UI is served alongside the webserver

[cicdw]

yea I should fix this prior to merging