Support dynamic generation of cacheKeyPrefix

[Tam2]

It would be good to dynamically generate the cacheKeyPrefix based on the incoming request

The use case would be to set the cacheKeyPrefix to the tenantId for the incoming request so each tenant has its own namespace for the keys

For us the tenantId would either be in the header or as part of the JWT based on how the user is authenticated

[mahendraHegde]

@Tam2 have you considered passing options to IdempotencyParams?
you can also refer this test case.

node-idempotency/packages/core/tests/e2e/idempotency.spec.ts

Lines 70 to 105 in e6259d6

	it("should allow overriding cacheKeyPrefix", async () => {
	const req: IdempotencyParams = {
	headers: { [HttpHeaderKeysEnum.IDEMPOTENCY_KEY]: "1" },
	path: "/pay",
	body: { a: "a" },
	method: "POST",
	options: {
	cacheKeyPrefix: "tenant-1",
	},
	};
	const res = { body: { success: "true" } };
	const idempotencyRes = await idempotency.onRequest(req);
	expect(idempotencyRes).toBeUndefined();
	await idempotency.onResponse(req, res);
	const cachedResponse = await idempotency.onRequest(req);
	expect(cachedResponse).toEqual(res);
	expect(
	await storage.get(`${req.options?.cacheKeyPrefix}:POST:/pay:1`),
	).toEqual(
	'{"status":"COMPLETE","fingerPrint":"f45aa7a9803525391d546d331b22b3ed4583a11a04797feaeb1027b158c65d10","response":{"body":{"success":"true"}}}',
	);
	// different tenant with same idempotency key
	const cachedResponse2 = await idempotency.onRequest({
	...req,
	options: {
	cacheKeyPrefix: "tenant-2",
	},
	});
	expect(cachedResponse2).toBeUndefined();
	});

let me know if you have any doubts.