* Add basic http metrics
* Implement custom http metrics
* Update docs

* feat: Add support for public projects (#2670)

* refactor: Extract complex SQL query into helper function

* fix: Keep list_user_projects backward compatible - Dakota pointed out that changing it to include public non-member projects could break existing code that assumes membership, so split into two functions

* test: Add service-level tests for backward compatibility

* refactor: Consolidate query logic with parameter approach

* Simplify project service functions for public project discovery

* Clean up inline comments in project service

* Fix code formatting for pre-commit compliance

* Add database migration for ProjectModel.is_public

* Fix code formatting for pre-commit compliance

* fix: clarify docstring for global admin behavior

* Fix public project access for non-members

* Apply pre-commit formatting fixes

* Fix comments and docstrings

---------

Co-authored-by: Victor Skvortsov <vds003@gmail.com>

Also refactor so that it is less likely that we
forget to associate new termination reasons with
retry events.

`dstack ps` used to show an incorrect error
message in case of volume errors.

Support rolling deployment when some service
configuration properties are changed. During the
deployment, `dstack` updates service replicas one
by one. It first starts a new version of the
replica, then waits until it is running, then
stops the old version of the replica.

As part of the implementation, introduce a new run
and job property - `deployment_num`. When a new
configuration is applied, the `deployment_num` of
the run is incremented. Then, `dstack` gradually
updates the jobs so that their `deployment_num`
matches that of the run. Some jobs are updated
in-place, if the new configuration does not affect
their spec, others are redeployed as described
above.

```shell
> dstack apply

Active run test-service already exists. Detected configuration changes that can be updated in-place: ['image', 'env', 'commands']
Update the run? [y/n]: y
⠋ Launching test-service...
 NAME                            BACKEND          RESOURCES                        PRICE    STATUS       SUBMITTED
 test-service deployment=1                                                                  running      11 mins ago
   replica=0 job=0 deployment=0  aws (us-west-2)  cpu=2 mem=1GB disk=100GB (spot)  $0.0026  terminating  11 mins ago
   replica=1 job=0 deployment=1  aws (us-west-2)  cpu=2 mem=1GB disk=100GB (spot)  $0.0026  running      1 min ago
```