v0.12.1

## Caddy config loading

After upgrading both CLI and machine daemons to v0.12.1, you can [redeploy Caddy](https://uncloud.run/docs/concepts/ingress/managing-caddy#deploying-or-updating-caddy) without using the `--watch` flag.

The Caddy config is now loaded automatically by the machine daemon via the Caddy Admin API. This allows to log errors and not overwrite the `Caddyfile` on disk if the config is invalid. `uc caddy config` should now return the latest config that was successfully loaded into Caddy.

## Unique context name for new clusters

When creating a new cluster, if the default context name `default` is already taken, a unique name like `default-1`, `default-2`, etc. will be generated automatically.

## Changelog
* 835834322b00759b67ae74e749e807894fdf7c8a chore: Add GH bug report template
* 9963f9df2d2bae424b52d9a5bcdb03de8b015ebe chore: Update bug template
* 5baa8087e548ef9fc3756228e3a776b80af17620 chore: load Caddy config via admin API instead of watching Caddyfile change on fs
* d25864e52f2cb3cb4eb7d29ac4f6f58a2b62a3f8 feat: automatically generate a unique 'default-N' context name for new cluster (fixes #113)
* ec2787c99cb771e592975f3e7f1ca8f5f1857320 fix: Handle implicit relative path for config
* 51ba3c7df84d9cf2d589ac022aa079b9af6ad6de fix: landing navbar on mobile
* 97bdb8eae161930f5e8c6002aedfc8752f3617bb fix: skip validation for user-defined Caddy configs if caddy not running locally
* 7b88b8b8102de6fbcee68a56a08755cec62f1e3a fix: write generated Caddyfile to disk only if succesfully loaded into local Caddy (means valid)