Run publishToMavenLocal as a dependency of build

[CRogers]

Before this PR

Similar to the myriad of problems we've had internally, we don't run publishToMavenLocal as part of build. It does current run as part of trial-publish, but I want to remove this circle job, as the internal version is useless (uses --dry-run) and is waste of resources/computing power (and I want internal + external to look similar).

This means (without trial-publish) the various publishable artifacts may never get built at PR time, so a change could break building some artifact, the PR build does not even build it, build is green, PR merges, publish breaks when it tries to build the artifact.

After this PR

==COMMIT_MSG==
Run publishToMavenLocal as a dependency of build to ensure publishable artifacts are built as part of PR builds and do not spuriously merge and then break publishing on develop.
==COMMIT_MSG==

Possible downsides?

[changelog-app]

Generate changelog in changelog/@unreleased

What do the change types mean?

• feature: A new feature of the service.
• improvement: An incremental improvement in the functionality or operation of the service.
• fix: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way.
• break: Has the potential to break consumers of this service's API, inclusive of both Palantir services
  and external consumers of the service's API (e.g. customer-written software or integrations).
• deprecation: Advertises the intention to remove service functionality without any change to the
  operation of the service itself.
• manualTask: Requires the possibility of manual intervention (running a script, eyeballing configuration,
  performing database surgery, ...) at the time of upgrade for it to succeed.
• migration: A fully automatic upgrade migration task with no engineer input required.

Note: only one type should be chosen.

How are new versions calculated?

• ❗The break and manual task changelog types will result in a major release!
• 🐛 The fix changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease.
• ✨ All others will result in a minor version release.

Type

• Feature
• Improvement
• Fix
• Break
• Deprecation
• Manual task
• Migration

Description

Run publishToMavenLocal as a dependency of build to ensure publishable artifacts are built as part of PR builds and do not spuriously merge and then break publishing on develop.

Check the box to generate changelog(s)

• Generate changelog entry

[svc-autorelease]

Released 1.13.0