feat: trigger image pull on mise.toml or mise.lock changes (#25400)

The dogfood Dockerfiles consume the repo-root `mise.toml` and
`mise.lock` at build time (see `.dockerignore` allowlist), but the
template's `pull_triggers` list ignored them, so mise-only changes (tool
bumps, new tools) didn't roll out to existing workspaces.

Mirror the `nix.hash` pattern: a Makefile rule writes the sha256 of both
files into `dogfood/coder/mise.hash`, and `main.tf` hashes that
in-module file via `filesha1`. Run `make dogfood/coder/mise.hash` after
editing `mise.toml`/`mise.lock`.

Signed-off-by: Thomas Kosiewski <tk@coder.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Makefile

@@ -1635,6 +1635,9 @@ endif
 dogfood/coder/nix.hash: flake.nix flake.lock
 	sha256sum flake.nix flake.lock >./dogfood/coder/nix.hash
 
+dogfood/coder/mise.hash: mise.toml mise.lock
+	sha256sum mise.toml mise.lock >./dogfood/coder/mise.hash
+
 # Count the number of test databases created per test package.
 count-test-databases:
 	PGPASSWORD=postgres psql -h localhost -U postgres -d coder_testing -P pager=off -c 'SELECT test_package, count(*) as count from test_databases GROUP BY test_package ORDER BY count DESC'

dogfood/coder/main.tf

@@ -829,6 +829,7 @@ resource "docker_image" "dogfood" {
     filesha1("ubuntu-22.04/Dockerfile"),
     filesha1("ubuntu-26.04/Dockerfile"),
     filesha1("nix.hash"),
+    filesha1("mise.hash"),
   ]
   keep_locally = true
 }

dogfood/coder/mise.hash

@@ -0,0 +1,2 @@
+b5226f4cb3256b5f67df1344f46968f7275b1b8309380506d25782168bab5622  mise.toml
+b5cf72024409932659abde978440fca1d01a75bb11f1476e2410f7d4b83aa9c0  mise.lock