Validation fails in RPC context for MqttContext about nest

[rbnayax]

@tolgap it shouldn't matter, but it was abused :-(

I suggest a diffrent thing:

export enum RpcParamtype {
  PAYLOAD = RouteParamtypes.BODY,
  CONTEXT = RouteParamtypes.HEADERS,
  GRPC_CALL = RouteParamtypes.FILES,
}

Working on a PR now.

[kamilmysliwiec]

cc @tolgap 👀

[rbnayax]

Same issue for RPC. RpcParamtype.CONTEXT value 6 used to be mapped to RouteParamtypes.HEADERS which was mapped to custom in ParamsTokenFactory . Now it is mapped to RouteParamtypes.PARAM.
The mentioned commit did introduce this regression but I think the issue here is not related to it, but to the fact that there is some sort of dependency between enum values across the packages which is not correct, and not enforced correctly. @kamilmysliwiec thoughts?

[rbnayax]

The type coercion here is the culprit

nest/packages/core/pipes/pipes-consumer.ts

Lines 13 to 15 in df37ea1

	const token = this.paramsTokenFactory.exchangeEnumForString(
	type as any as RouteParamtypes,
	);

[tolgap]

Wasn't aware that the position was this important for this. @kamilmysliwiec do we revert in the meantime then come back to this?

[rbnayax]

@tolgap opened #13351 this should revert to the original behavior