Nginx server config: JS was not compressed

[brontolosone]

Closes #819

See #819 for details.

What has been done to verify that this works as intended?

• Tested on my local docker setup. (size-1500+ bytes) JS responses get compressed now.

Why is this the best possible solution? Were any other approaches considered?

I considered removing the application/x-javascript compressible type as it is severely deprecated. But who knows, perhaps some circus member proxied by nginx emits headers with that Content-Type, and in that case we'll want to compress it. It doesn't hurt to keep it around just in case.

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

Intentional changes: Faster and cheaper cold cache load.
Regression risk assessment: Low

Does this change require updates to documentation? If so, please file an issue here and include the link below.

No

[matthew-white]

Thank you!