refactor: slightly optimize ConstructorConstructor

[MukjepScarlet]

Purpose

Part of #2864

Description

lambda -> method reference (reduce synthetic methods)
duplicated lambdas -> a class

Checklist

• New code follows the Google Java Style Guide
  This is automatically checked by mvn verify, but can also be checked on its own using mvn spotless:check.
  Style violations can be fixed using mvn spotless:apply; this can be done in a separate commit to verify that it did not cause undesired changes.
• If necessary, new public API validates arguments, for example rejects null
• New public API has Javadoc
  • Javadoc uses @since $next-version$
    ($next-version$ is a special placeholder which is automatically replaced during release)
• If necessary, new unit tests have been added
  • Assertions in unit tests use Truth, see existing tests
  • No JUnit 3 features are used (such as extending class TestCase)
  • If this pull request fixes a bug, a new test was added for a situation which failed previously and is now fixed
• mvn clean verify javadoc:jar passes without errors

[MukjepScarlet]

@eamonnmcmanus Please review this. Because I'm not Android developer, I'm not sure if these are benificial with Proguard/R8.

[Marcono1234]

Thanks a lot!

The idea to add an ExceptionObjectConstructor is really good to reduce the code duplication. I have just a few small suggestions.

The project members might have additional change requests though.

[eamonnmcmanus]

Thanks for this! I checked that it passes all of Google's internal tests.