infra: API responses should be cached (until a new build of the Hub API is published)

Through a mechanism like ETag or API Gateway's cache cluster, allow Meltano to cache API responses from the Hub, which are invalidated when a new build of the Hub is published.

This would save bandwidth on both ends: the Hub serving plugin definitions and Meltano requesting them.