feat: support automated hw probe adoption - #151

In `@src/extensions/endpoints/unadopted-probes/.mocharc.json`:
- Around line 5-8: Remove the deprecated Node flag
"experimental-specifier-resolution=node" from the "node-option" array in the
.mocharc.json for unadopted-probes so tests run on Node 22; leave the
"loader=ts-node/esm" entry (or remove the entire "node-option" array if nothing
else is needed) and ensure any custom CommonJS resolution is handled by a proper
ESM loader instead of that flag.

In `@src/extensions/endpoints/unadopted-probes/package.json`:
- Line 3: The package.json currently contains a placeholder description value
("Please enter a description for your extension") which must be replaced with a
meaningful description; open the package.json and update the "description" field
to a concise, accurate summary of the extension's purpose and functionality
(replace the placeholder string in the "description" property) so the manifest
conveys what the unadopted-probes extension does.

In `@src/extensions/endpoints/unadopted-probes/src/index.ts`:
- Around line 81-108: The adoption flow currently constructs new
services.ItemsService('gp_probes', { schema: await getSchema() }) without
passing accountability and does a read-then-update which allows race conditions;
fix by constructing ItemsService with the current request accountability (pass
accountability: req.accountability) and replace the separate read + updateOne
sequence with an atomic conditional update (or transaction/row-lock) that only
sets userId when the probe is still unclaimed—e.g. perform an update where id =
probe.id AND userId IS NULL (and optionally verify
JSON_VALUE(localAdoptionServer,"$.token") = req.body.token) and check the
affected row count to determine success, then readOne only after a successful
conditional update.

In `@src/extensions/endpoints/unadopted-probes/test/index.test.ts`:
- Around line 149-156: The test currently compares the entire probeData object
(probeData) to the response body for the GET '/valid-token-123' request, but the
endpoint only returns a subset of fields (country, city, network, ip); update
the assertion to stub/expect only those selected fields instead of the full
probeData. Locate the test case in index.test.ts (the "should return probe
details if token matches" test), replace the full-body equality check with an
assertion that res.body has only the keys country, city, network, ip and that
their values match the corresponding values from probeData (or construct an
expected object with just those four fields) so accidental data exposure is not
masked. Ensure you still assert status 200 and use the existing clientIp header
setup.
- Around line 11-20: The linter flags the intentional then property on the test
stub (dbStub.then), so leave the then stub as-is but add a Biome suppression
comment directly above the then property declaration to silence
lint/suspicious/noThenProperty; locate the dbStub object (symbol: dbStub) and
add the exact comment "// biome-ignore lint/suspicious/noThenProperty:
intentional thenable for test stub" immediately before the "then:
sandbox.stub()," entry so tests can use dbStub.then.yields(...) without lint
errors.

In `@src/extensions/lib/src/client-ip.ts`:
- Line 6: The direct JSON.parse of process.env.SERVER_TRUSTED_PROXIES (assigned
to trustedProxies) can throw at module load and crash the app; wrap the parse in
a try/catch, validate the input is present, and on parse failure set
trustedProxies to an empty array and emit a clear warning/error that includes
the problematic env value and parse error details so startup continues safely.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@Dockerfile`:
- Around line 72-73: The Dockerfile copies the built extension named
"local-adoption" but places it into /directus/extensions/unadopted-probes/,
causing a name mismatch; update the two COPY instructions that reference the
built artifacts (the lines copying from
/builder/src/extensions/endpoints/local-adoption/dist/* and the package.json) to
use the destination folder /directus/extensions/local-adoption/ so the runtime
folder matches the package.json "name": "local-adoption".

In `@src/extensions/endpoints/local-adoption/test/index.test.ts`:
- Around line 11-20: The test's Knex mock defines a literal "then" property on
knexQueryBuilder which trips Biome's noThenProperty rule; fix by adding a scoped
disable comment immediately above the then property in the knexQueryBuilder mock
(i.e., a single-line biome/noThenProperty disable for that property) so the
linter ignores only that occurrence, or alternatively replace the stubbed then
with a Promise-based mock (e.g., have the query builder methods return
Promise.resolve(...) or a function that returns a Promise) to avoid a raw then
property; update the entry named then on knexQueryBuilder accordingly.

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@test/e2e/tests/probes.spec.ts`:
- Around line 204-205: Replace brittle hard-coded waits: where the test calls
page.waitForTimeout(...) immediately before clicking the "Adopt the probe
manually" button, remove the waitForTimeout and assert the button's visibility
using Playwright's web-first assertions (e.g., use
expect(page.getByRole('button', { name: 'Adopt the probe manually'
})).toBeVisible() ), then perform the click; apply the same change to the other
instances that use page.waitForTimeout before interacting with that button (same
pattern also applies to the similar wait before the adoption code test).