refactor(telemetry): rename Workflow Insight to Durable Execution Telemetry - #1019

Rename the insight-plugin module to telemetry-exporter, the artifactId to
aws-durable-execution-sdk-java-plugin-telemetry-exporter and the Java package to
software.amazon.lambda.durable.telemetry. Rename the public API, the recordType
discriminator and the default resource names to match the JavaScript SDK
(aws/aws-durable-execution-sdk-js#1019). Old names are no longer accepted.

By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.

### Issue Link, if available

Stacked on #1019. This PR targets `rename-insight-to-telemetry` and
should merge after #1019.

Replaces #1029 with a branch in `aws/aws-durable-execution-sdk-js`. Both
PRs contain the same commits through `31503917`.

### Description

- Bump the telemetry exporter and MCP packages from `0.1.0-alpha.0` to
stable `1.0.0`. Update their root lockfile entries.
- Remove all 41 exporter `@experimental` annotations. MCP has no such
annotations.
- Remove the repository README sentence describing Durable Execution
Telemetry as preview.

Runtime implementations, API signatures, and other package versions are
unchanged.

### Demo/Screenshots

Not applicable. These changes affect package metadata and documentation.

### Checklist

- [x] I have filled out every section of the PR template
- [x] I have thoroughly tested this change

### Testing

- Node 22: full `npm run build` and `npm run test` passed.
- `lint:ci`, `lint:versions`, `lint:filenames`, `lint:suppressions`, and
`typecheck:hosts` passed.
- Packaging checks passed for both packages. All 32 declaration files in
the exporter tarball contain no experimental annotations.
- Five temporary stability checks and five release checks passed. The
built MCP server reports `1.0.0` during initialization.

#### Unit Tests

5,141 Jest tests passed, with six existing skips. Two Vitest tests
passed. These totals include 81 exporter tests and 404 MCP tests.

No runtime behavior changed. Focused metadata and documentation checks
ran outside the repository; no source test files were added.

#### Integration Tests

Local integration tests passed through `npm run test`. Cloud tests were
not run. No deployment or npm publication was performed.

#### Examples

Not applicable. No public API or example behavior changed.

### CI note

The same-repository head removes the fork restriction on integration
tests. The build workflow still only matches PR bases `main` and `v1.x`.
The usual build and integration workflow will not run while this PR
targets the parent branch.

---------

Co-authored-by: Pooya Paridel <[email protected]>

Rename Workflow Insight to Durable Execution Telemetry, as the
JavaScript SDK does in aws/aws-durable-execution-sdk-js#1019. The
explorer and MCP server of the JavaScript SDK read the records of every
SDK, so the persisted values must match. The old names are not
accepted.

- The insight module is now the telemetry module, at
  github.com/aws/aws-durable-execution-sdk-go/telemetry, with package
  telemetry. Its display name is Durable Execution Telemetry Exporter.
- InsightPlugin is now TelemetryPlugin. Other exported names keep their
  names in the new package.
- recordType is "DurableExecutionTelemetry". The default prefixes and
  index are durable-execution-telemetry, the default tables
  durable_execution_telemetry, and the default EventBridge source
  aws.durable-execution.telemetry.
- The insight-plugin example is now telemetry-exporter.
- The release tool, CI, scripts, and docs use the telemetry module and
  its telemetry/vX.Y.Z tags. The insight module was never tagged.
- The release notes record the rename.