Regenerate Google Tasks client with corrected operation name

## Description

Regenerate the Google Tasks TypeScript connector using the latest CodefulSdkGenerator from AzureUX-BPM.

The Google Tasks Swagger contains the misspelled operation ID `CraeteTask`. The shared generator correction now normalizes this to `CreateTask` before language-specific generation, producing:

- Before: `GoogletasksClient.craeteTaskAsync`
- After: `GoogletasksClient.createTaskAsync`

The connector route and request payload remain unchanged.

## Context

- AzureUX-BPM generator revision: `1b7f7d412f648631f9303528a8af8af798918a57`
- Pinned Swagger: `swagger-cache/googletasks.swagger.json`
- Swagger SHA-256: `0c7f04201868f4f31b01a72191cf9c28617bf09cb07265ef1bab75723c20efb6`
- Existing regeneration commit: `29efa9f5e0955243c07702e2288c1606455be315`
- The generated client and focused test are updated, but `generation.manifest.json` still contains the previous Google Tasks output hash.

## Acceptance Criteria

- [ ] Regenerate `src/generated/GoogletasksExtensions.ts` from the pinned Swagger.
- [ ] Confirm the client exposes `createTaskAsync`, not `craeteTaskAsync`.
- [ ] Update `generation.manifest.json` with the immutable BPM revision, assembly version, generation timestamp, and canonical output hash.
- [ ] Confirm the manifest provenance test passes.
- [ ] Run `npm run build`.
- [ ] Run `npm run typecheck`.
- [ ] Run `npm test`.
- [ ] Run `npm run typecheck:samples`.

Start with swagger-cache/googletasks.swagger.json, src/generated/GoogletasksExtensions.ts, and generation.manifest.json, using the pinned Swagger and AzureUX-BPM revision in the issue. Review existing regeneration commit 29efa9f5e0955243c07702e2288c1606455be315, then run the provenance test and npm run build, npm run typecheck, npm test, and npm run typecheck:samples. Done means the corrected client method and manifest metadata/hash are accepted by all listed checks.

Written by the indexing model from the issue text.