refactor!: rename the project from Monitor to MoShiro

Namespaces, assemblies, projects and directories, the solution, binaries,
images, systemd units, config paths, environment variables, protocol method
names, the media type and the raw chunk magic all move to MoShiro/moshiro.
Existing data and deployments are not compatible and must be recreated.
Also fix the architecture tests after the solution layout change and make
the update tests independent of their order.

web/shared/api/source.ts

@@ -1,10 +1,10 @@
 /**
  * 数据源：前端默认和后端同源（Cookie 会话）。也可以指到别的后端（如本机跑前端、连线上的 `https://mo.oeo.one`）：
  * 地址和令牌存在浏览器里（每个前端各存一份令牌），也可以用构建时的 `VITE_API_BASE` 给个默认地址。
- * 跨域时不带 Cookie，只用 `Authorization: Bearer <API 令牌>`；后端要在 `Monitor__CorsOrigins` 里放行这个前端的来源。
+ * 跨域时不带 Cookie，只用 `Authorization: Bearer <API 令牌>`；后端要在 `MoShiro__CorsOrigins` 里放行这个前端的来源。
  */
 
-const BASE_KEY = 'monitor.api_base'
+const BASE_KEY = 'moshiro.api_base'
 
 let app = 'app'
 
@@ -48,7 +48,7 @@ export interface SavedSource {
 }
 
 // v2：以前保存的是手填的管理 Token，现在是登录后拿到的会话，旧的不再使用
-const listKey = () => `monitor.sources.v2.${app}`
+const listKey = () => `moshiro.sources.v2.${app}`
 
 function readList(): SavedSource[] {
   try {