Check eclipse collection api factory

[Shibi-bala]

Before this PR

We've seen this deadlock issue on a service where this package was the root cause. Adding an errorprone rule for this.

Full description of issue is here: palantir/atlasdb#7073

After this PR

==COMMIT_MSG==
==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

Check eclipse collection api factory

Check the box to generate changelog(s)

• Generate changelog entry

[Shibi-bala]

I can't find an errorprone rule that deals with libraries we don't like. I suppose because that is pretty opinionated.

Anyway, decided against making this check too generic (supporting other bad imports and fixes) since there would be a lot of abstraction written for one case (so far) to be able to support various ways of fixing issues.