fix: double decode params in cluster methods middleware

[Assem-Uber]

Summary

Next.js App Router already decodes dynamic route params before passing them to API routes & our custom middlewares. This change removes redundant decoding in the gRPC cluster methods middleware so we don’t double-decode and avoid URIError or corrupted values (e.g. workflowIds 100% or @).

Changes

• Removed decodeUrlParams import and usage; middleware now uses params from the handler as-is and passes params.cluster directly to getClusterMethods().
• Removed decodeUrlParams mock and all assertions that it was called; tests now assert that getClusterMethods is called with mockParams.cluster and that params are passed through unchanged.

Fix Plans

• Fix custom middleware double decoding ✅
• Fix Summary page/apis double decoding
• Fix tasklist page/apis double decoding
• Fix workflow query diagnostics api double decoding
• Fix workflow actions double decoding
• Fix domain page/apis double decoding

Testing

• Tested opening workflow with special characters in workflowId http://localhost:8088/domains/default/cluster0/workflows/%23%24%40%5E%25%24%40%5E%23%25%24%5E%26%40/e00efb14-c148-4f48-be8f-f4fc066e2d97/summary

• Error before the fix:

• Error no longer happens, while the page is still not loading due to double decoding happening in other pages that is going to be addressed in next PRs.
• Logging nextjs params from within the middleware, shows it is already decoded

[Copilot]

Pull request overview

Removes redundant URL parameter decoding from the gRPC cluster methods route-handler middleware to avoid double-decoding issues with Next.js App Router dynamic route params (e.g., %, @) and updates tests accordingly.

Changes:

• Removed decodeUrlParams usage in grpcClusterMethods and passed params.cluster through directly to getClusterMethods.
• Updated middleware unit tests to stop mocking/asserting decodeUrlParams and instead assert pass-through behavior.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
src/utils/route-handlers-middleware/middlewares/grpc-cluster-methods.ts	Stops decoding params in the middleware and forwards params.cluster directly to getClusterMethods.
src/utils/route-handlers-middleware/middlewares/tests/grpc-cluster-methods.test.ts	Removes decodeUrlParams mocking/assertions and validates getClusterMethods is called with the raw params.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Local variable name clusterMetods appears to be misspelled (missing the 'h'). Renaming it to clusterMethods would improve readability and avoid propagating the typo in future edits.

Suggested change

	const clusterMetods = await getClusterMethods(params.cluster, grpcMetadata);
	return ['grpcClusterMethods', clusterMetods];
	const clusterMethods = await getClusterMethods(params.cluster, grpcMetadata);
	return ['grpcClusterMethods', clusterMethods];

[Copilot]

The rejection assertion in the preceding test is wrapped in an extra expect(...)/await (i.e., await expect(await expect(promise).rejects...)), which adds no assertion and makes the test harder to read. Consider simplifying to a single await expect(grpcClusterMethods(...)).rejects....