Don't always inline expression lambdas

[dansanduleac]

Before this PR

We always allow an inlining to stop at a lambda, regardless of the complexity of the expression following the lambda.

This can sometimes lead to inlining a bunch of arguments but breaking up a super simple lambda, which is not readable at all:

publisher = new ThisThatEventPublisher(
        txnManager, () -> Events.encoder(keyPair, new TestClock()), EventSeries.THING, () ->
                DEFAULT_EVENT_BATCH_SIZE);

After this PR

==COMMIT_MSG==
More strictly control when we can inline a chunk of code followed by an expression lambda.

Specifically, the inlining chain now continues through to the body of the expression lambda, with the exception that the inlined expression so far is reset to be considered "simple" when entering a lambda expression.

The exception is necessary in order to preserve the inlining of palantir-chains-lambdas which we consider desirable.
==COMMIT_MSG==

Example changes on:

• conjure-java-runtime

Possible downsides?

• Inadvertently changing more code that looked better before.
  I think this is acceptable as long as the existing code doesn't become less readable but just a bit more sparse, if in return we get rid of some corner cases that were extremely unreadable / confusing.

[changelog-app]

Generate changelog in changelog/@unreleased

Type

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

Description

More strictly control when we can inline a chunk of code followed by an expression lambda, to avoid pathological cases with a very simple expression being split onto the next line.

Check the box to generate changelog(s)

• Generate changelog entry

[dansanduleac]

Holding off on this for a bit until we can determine how many changes it will cause in a large internal repo.

[svc-autorelease]

Released 0.3.19