fix(agiloft): regenerate tool metadata and drop a JWT-shaped test fixture

Two CI failures, both mine.

The generated tool metadata was stale: this branch reworded the create record
fields output, which feeds it. Regenerated - the only entry that changes is
agiloft_create_record.

The login token-integrity test built its fake token from a real JWT header
segment, which reads as a live credential to secret scanning. The test only
needs an opaque value that happens to contain the password, so it uses one
that cannot be mistaken for a token.

Author: mzxchandra

apps/sim/tools/agiloft/utils.server.test.ts

@@ -174,8 +174,13 @@ describe('agiloftLoginPinned token integrity', () => {
    * break every request that carries it, so parsing stays on the raw text.
    */
   it('returns the token intact when the password occurs inside it', async () => {
+    /**
+     * Deliberately not JWT-shaped: a realistic header segment reads as a real
+     * token to secret scanners. All this test needs is an opaque value that
+     * happens to contain the password.
+     */
     const password = 'abc'
-    const token = `eyJhbGciOiJIUzI1NiJ9.${password}payload.signature`
+    const token = `opaque-session-value-${password}-trailing`
 
     mockSecureFetch.mockResolvedValueOnce(
       mockResponse({ json: { access_token: token, authentication_scheme: 'Bearer ' } })