[CX] Shrink impact of Analytics on installer size

Summary: Analytics takes an undue proportion of the overall size of Couchbase Server, which is causing issues due to slowness creating and transferring bloated installers.

Request: Find some way to make large portions of Analytics not required to be shipped inside the installer.

Supporting details:

Comparing the CE and EE builds of 7.1.0-1234, I find:

1. The installer sizes (Ubuntu 20.04) are 257MB vs. 657MB (155% larger)
2. The on-disk sizes are 769MB vs. 1445MB (87% larger)
3. The differences on disk are:
   1. 100 MB in bin, comprising these tools: backup cbas cbevent cbsummary eventing-consumer eventing-producer js-evaluator magma_dump plasma_dump (the lion's share are eventing-producer at 28MB and backup at 20MB)
   2. 570MB in lib, entirely within "cbas"

So Analytics is responsible for ~40% of the on-disk size and ~55% of the installer size.

Those numbers would drop if MB-48381 is resolved, but even prior to the addition of the aws-sdk jar, the numbers were close to 30% of the on-disk size and 40% of the installer size.

FYI in all cases the included JRE is 146MB on-disk, or about 42% of the overall Analytics on-disk foot print before aws-sdk.

The installer size impact is actually a bigger problem than the on-disk impact, because it has an outsize effect on overall build times. In a recent Neo build, the Centos 7 EE build took 27 minutes just to create the rpm. The same CE build took 5 minutes. I know there are other issues there that Build can possibly address, but the difference is still stark. That is why I'm filing this as "Critical" even though it is technically just an Improvement.