Schema updates between app versions are problematic and would require a
much more complicated versioning/compatibility mechanism, so forget
about them, and therefore do away with hard-coded ETags for bundled
schema files. Consumers that only download the schema file from the API
can get the initial ETag from the API.