[Safe-logging] Infer lambda parameter safety from surrounding context

[aldexis]

Before this PR

Using a lambda's parameter as safe when we know it is unsafe isn't caught.

Unfortunately, the lambda parameter types passed in SafetyPropagationTransfer#initialStore from ForwardAnalysisImpl#getParameters don't seem to contain the type annotations. However, they are present in the underlyingAst argument which is also given, so we can instead recompute the argument safety from the expected lambda type.

After this PR

Builds on top of #3048, which handles checking the returned values in a lambda

==COMMIT_MSG==
[Safe-logging] Infer lambda parameter safety from surrounding context
==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

[Safe-logging] Infer lambda parameter safety from surrounding context

Check the box to generate changelog(s)

• Generate changelog entry

[carterkozak]

Great work, especially the test coverage!

[autorelease3]

Released 6.15.0