🚀 Feature: Configure Client-Side Cache Control For Storage

### 🔖 Feature description Cache headers (ETag, Max-Age,..) should be configurable for files in Storage. This can be done in the following ways: 1) There's a config dialog in the console to set global cache options for a bucket or file 2) On upload, file-specific cache settings can be send as part of the API request, which overwrite settings from 1) 3) On download, cache settings can be requested, which overwrite settings from 1) and 2) ETag may be selectable as static value, hash or date. ### 🎤 Pitch Depending on usage of files stored in the Storage, files may have different caching requirements for optimal user experience. A customer should be able to tune caching to their needs with global defaults and fine-grained control. For example, an avatar image may be cached for hours to days, while diagrams may need to be refreshed more frequently. Logos or documents may even be cached for weeks! Allowing control over the headers is a simple and efficient way to enable this feature while not costing any additional resources. ### 👀 Have you spent some time to check if this issue has been raised before? - [X] I checked and didn't find similar issue ### 🏢 Have you read the Code of Conduct? - [X] I have read the [Code of Conduct](https://github.com/appwrite/.github/blob/main/CODE_OF_CONDUCT.md)