Fix: Align Cache API definitions with Storage spec (#1789)
* Fix: Align Cache API definitions with Storage spec
This commit clarifies how the Cache API interacts with the underlying
storage mechanism, resolving ambiguity that stemmed from previous
specification language.
Key changes:
- Removes the direct association between "storage key" and "name to
cache map".
- Defines "relevant name to cache map" as being retrieved via the
`obtain a local storage bottle map` algorithm from the Storage
specification, ensuring alignment.
- Updates the definition of `CacheStorage` to represent the
`name to cache map` associated with its `environment settings object`,
rather than the `origin`.
- Clarifying the definition of "relevant name to cache map" and its relationship with `CacheStorage`.
- Removing the explicit ID and avoiding indirect `[=this=]` usage.
- Ensuring consistent syntax for `[=name to cache map=]` references.
This makes the relationship between the ServiceWorker Cache API and the
Storage specification explicit and consistent, addressing the core issue
raised in https://github.com/w3c/ServiceWorker/issues/1784 and the follow-up
work in https://github.com/w3c/ServiceWorker/issues/1788.