GraphQL introspection may not be "disableable" in prod

[justincorrigible]

As noticed by @evans-g-crsj, Arranger's GraphQL endpoints seem to expose their schema introspection while on 'production' environments, even though those are meant to be disabled by default.

Doing research into possible causes, I've confirmed the latest of legacy Arranger Server (currently v2.16.2) depends on Apollo package version that should work.
This package claims to do the trick.
However, that package's logic is present in our (outdated) version of Apollo, so it should already be doing this internally but it isn't, which is puzzling.

Speculation: there's an internal dependency conflict, where arranger-server-core (the module that contains the "fix") is being overridden/replaced somehow with a version that doesn't allow disabling introspection.