Kanban 2052: fetch the matching LIMS product manifest during TeamCity builds

[labkey-willm]

Rationale

The plan was always to pull the correct product manifest in during the container build (e.g. LabKey_267Release_Internal_FinalRelease_CloudInfrastructure_LimsStarterContainer), but that predates distributions#613 splitting one lims_starter manifest into several fine-grained product manifests, and the fetch itself was never actually implemented - startup/manifest.properties was just the ${LABKEY_STARTUP_DISTRIBUTION_EXTRA} envsubst placeholder with nothing setting it. Adds the fetch, generalized by LABKEY_DISTRIBUTION so both the existing lims_starter container build and a future lksm_professional sibling can use the same mechanism. This is a public repo, so the fetch only runs under LabKey's own TeamCity (or with an explicit local opt-in) - a community/external build has no access to, and no use for, the internal LIMS manifest bucket.

Related Pull Requests

• LabKey/syseng-chef-server#684 (same list-and-match approach, for the EC2/chef side)
• LabKey/terraform_services#76

Changes

• Add a fetch-manifest Makefile target, made a prerequisite of build, that lists the product's S3 prefix in labkey-lims-manifests and fetches whichever single manifest is there into startup/manifest.properties
• Only runs when TEAMCITY_VERSION is set, or with FETCH_LIMS_MANIFEST=1 for local testing - otherwise a no-op
• Also a no-op for any LABKEY_DISTRIBUTION with no manifest published (community, enterprise, allpg, etc.) - no allowlist needed