CACHE-13371: more cache knobs under request.cf object

[yj7o5]

This PR adds new cache fields under the request cf object to allow more fine grained control to workers fetch API for caching assets.

[danlapid]

Let's add new code behind an featureFlags.getWorkerdExperimental() check until we validated that it works as we want in prod, then we can delete the gate.

[danlapid]

This shouldn't work, are you sure the tests are testing what you want?
It should need to be

Suggested change

	compatibilityFlags = ["nodejs_compat", "service_binding_extra_handlers", "cache_option_disabled", "url_standard", "workers_api_getters_setters_on_prototype", "fetch_legacy_url", "web_socket_auto_reply_to_close", "workerd_experimental"],
	compatibilityFlags = ["nodejs_compat", "service_binding_extra_handlers", "cache_option_disabled", "url_standard", "workers_api_getters_setters_on_prototype", "fetch_legacy_url", "web_socket_auto_reply_to_close", "experimental"],

[harrishancock]

Do we need to check for negative numbers here? The comment on line 758 suggests a contract.

[codspeed-hq]

Merging this PR will degrade performance by 11.15%

❌ 1 regressed benchmark
✅ 69 untouched benchmarks
⏩ 129 skipped benchmarks¹

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Benchmark	BASE	HEAD	Efficiency
❌	Encode_ASCII_32[TextEncoder][0/0/32]	3.1 ms	3.5 ms	-11.15%

---

_{Comparing yj7o5:yawar/CACHE-13371_add-cf-cache-control-field (3096570) with main (329f6d4)}

Footnotes

1. 129 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩