Bump spring-boot-gradle-plugin from 2.2.0.RELEASE to 2.2.1.RELEASE

[dependabot-preview]

Bumps spring-boot-gradle-plugin from 2.2.0.RELEASE to 2.2.1.RELEASE.

Release notes

Sourced from spring-boot-gradle-plugin's releases.

v2.2.1.RELEASE

📣 Notes

• @ConfigurationProperties scanning is now disabled by default and needs to be explicitly opted into by adding the @ConfigurationPropertiesScan annotation. More details related to this change can be found here.

⭐ New Features

• Support constructor binding for property nested inside a JavaBean #18894
• Support amqps:// URIs in spring.rabbitmq.addresses #18885
• Add config property for CodecConfigurer.maxInMemorySize in WebFlux #18828
• Make test slices' type exclude filters public #18746

🪲 Bug Fixes

• Recursive property in @ConfigurationProperties causes java.lang.StackOverflowError when generating metadata #18889
• Endpoint filter configured on an endpoint's super-class has no effect #18882
• Dependency relationships created by AbstractDependsOnBeanFactoryPostProcessors cannot be overridden #18878
• HazelcastHealthContributorAutoConfiguration not bootstrapped #18847
• Dependency management has unnecessary log4j exclusion for spring-cloud-spring-service-connector #18833
• Constructor binding for nested class with multiple constructors causes BindException #18810
• Reactive health indicators are ignored in MVC applications #18805
• Failure analysis description for BeanDefinitionOverrideExceptions includes useless information when a bean definition has no resource description #18749
• Reactive HealthContributors do not hide non-reactive ones #18748
• configprops error when jobscope defined in configuration #18714
• Confusing error message if property not found when ConstructorBinding is used #18704
• Make optimizedLaunch property name more consistent #18702
• It is unclear that server.tomcat.max-http-post-size and server.jetty.max-http-post-size only apply to POSTed form content #18695
• NPE is thrown from /actuator/health with an empty composite contributor #18687
• /actuator/health returns 404 if no indicator is present #18676
• @TestConfiguration disables proxying of @Bean methods #18675
• Enabling configuration properties scanning by default prevents conditional registration of @ConfigurationProperties-annoted types that are found by scanning #18674
• Depends on semantic between Liquibase and JPA are no longer applied with custom SpringLiquibase #18673
• Bean validation not picking error translations anymore #18672
• Binding fails in presence of a synthetic constructor #18670
• Application does not start anymore with only AbstractRoutingDataSource beans #18661
• ConfigurationProperties with constructor binding cannot be mocked #18652
• Actuator health check groups allow to specify checks only in lower case #18649
• Immutable configuration properties not shown by Actuator #18636
• Use of CGLib proxies is only auto-configured when AspectJ is on the classpath #18523

📔 Documentation

• Spring boot tests overrides surefire plugin listeners #18893
• Logs of java.util.logging.Logger are not output when war is deployed to tomcat. #18880
• Document that @Order cannot be used on a Filter's @Bean method to set the Filter's order #18879
• Unexpected settings in effective pom when inheriting from spring-boot-starter-parent #18877
• Improve security-related recommendations for DevTools' remote application support #18876
• Document Settings as jooq supported auto-configuration type #18875
• Add reference to Armeria starter #18837
• Make "Containers and Exploded Archives" section more visible #18818

... (truncated)

Commits

• 2c9cf65 Release v2.2.1.RELEASE
• 75f210a Merge branch '2.1.x'
• 8d3df1b Make CI credentials requirement lenient when building RestTemplate
• 1429344 Merge branch '2.1.x'
• 891c712 Wait for distribution to reach Bintray before checking its completeness
• 86a1c96 Make sure health endpoint is available with no contributor
• f57baa7 Merge branch '2.1.x'
• 8b1ff0a Next development version (v2.1.11.BUILD-SNAPSHOT)
• 684d7cf Upgrade to Mongodb 3.11.2
• a31874c Merge branch '2.1.x'
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)