v1.18.2

# Changelog

The two main features of this release are **Linked Repos** and **Alert Maintenance Windows**.

## Repo Linking

For Repo linking, this means you can link Repos that you configure once in Komodo to *multiple resources*. This avoids having to configure your repo provider, name, and account multiple times (you can just select it in the dropdown), and also keeps things in sync if you change the underlying repo provider, name, branch, or account. This is available on all Resources that use git repos (`Stacks`, `Builds`, and `Resource Syncs`).

For Stacks, this means that multiple Stacks attached to the same Repo will **share the same repo clone on individual hosts**. You can migrate your Stacks to used the linked Repo in place, just note that it won't deal with any data mounted inside the clone folders. Those would need to be moved to the new Repo clone path (as specified in the Repo config). Ideally all your data mounts are outside of the repo. Config files which are committed inside the repo are fine to keep mounted in using relative path however.

Note that you can but don't need to attach a Server / Builder to the Repo. If you do configure an attachment on the Repo, the Repo can still be attached to Stacks on other Servers. The Repo server / builder attachments aren't considered by Resources depending on the Repo. 

## Alert Maintenance Windows

These allow you to configure time periods to suppress alerts when downtime is expected, such as for system updates. You can schedule either Daily, Weekly, or One Time maintenance windows, and configure them on individual `Servers` and `Alerters`.

### Resource

- **Server**: Add docker lists search re #548 
- **Server**: Add Periphery version indicator to Server tables
- **Deployment / All containers**: Support capitals and `.` in the names re #563 
- **Actions**: Add `komodo.execute_container_exec`, `komodo.execute_deployment_exec`, `komodo.execute_stack_exec` methods
    - Similar to `komodo.execute_terminal`, but set up to connect directly to container exec
    - Only requires `disable_container_exec = false` in Periphery config. Direct terminals can be disabled.
- **Stack, Build, Resource Sync**: Can now link **Komodo Repos** (in the sidebar) directly to these resources
    - **Stacks**: Have them share a single repo clone on your hosts.
    - *Don't* need to attach Repo to any Server / Builder, but you can if you would like, to manually pull / reclone.
    - *Note*: Non admin users need `Attach` permission on the Repo to be able to link Resources to it.
- **Server / Alerter**: Add per-server and per-alerter maintenance window configuration to suppress alerts during planned time periods. #550 by @R3D2 and @mbecker20 

### Misc

- Failed OIDC provider initialization just error logs, doesn't crash core. Can still login with other providers. Re. #567 
- OIDC login gets username using the standard `userinfo` endpoint, instead of token claims. Does not affect already created users in Komodo, only new users. Re. #557