Bump archunit-junit5-engine from 0.16.0 to 0.17.0

[dependabot]

Bumps archunit-junit5-engine from 0.16.0 to 0.17.0.

Release notes

Sourced from archunit-junit5-engine's releases.

ArchUnit 0.17.0

Breaking Changes

• The metaAnnotatedWith(..) predicate, as well as all syntax elements like classes().that().areMetaAnnotatedWith(..) or classes().should().beMetaAnnotatedWith(..), now all also count direct annotations as matching. The background is, that the typical use case always seemed to be "either directly annotated or annotated with some meta-annotated annotation", so we decided to cover this directly.
  • If your rule has metaAnnotatedWith(..).or(annotatedWith(..)) it still works, but you can now drop the annotatedWith(..) part
  • If your rule really wanted to test that the annotation is not a direct annotation, but only meta-annotated on another annotation, this can still be asserted by metaAnnotatedWith(..).and(not(annotatedWith(..))) (see #527)

Enhancements

• Classes appearing in member signatures (like field types or method return values) are now automatically resolved in import (see #530)
• Support for Java 17 (see #535)
• New API to check if a JavaAnnotation has explicitly declared a certain property, i.e. it is set in the annotation and not taken from the default value (see #499)

Lang

• Improved Javadoc and error message to better explain the difference of classes().that().implement(..) and classes().that().areAssignableTo(..)

Library

• New rule to assert no proxy bypasses, e.g. if a Spring bean internally calls an @Async method and thus bypasses the proxy (see #539)

JUnit

• We decided to rename ArchRules.in(..) to ArchTests.in(..), because ArchRules was considered confusing, if the actual behavior is to collect all @ArchTest members of the other class. ArchRules is still present (yet deprecated), so this will not break existing ArchTest suites (see #525)

Commits

• 937a9cc fix invalid Javadoc
• 192bc02 prepare release 0.17.0
• ad30fa5 Make meta annotated match direct annotations as well #540
• 71835ef add tests for classes().should().{be/notBe}MetaAnnotatedWith(..)
• 5d68c45 make metaAnnotated predicates also match direct annotations
• d37e2d0 Add library rule to check proxy bypasses #539
• f3ec2eb add library rule to check for classes bypassing their proxy
• e19c842 rename assertThat(ArchRule) -> assertThatRule(ArchRule)
• 61a1c9e introduce ArchTests instead of ArchRules #538
• dac33a3 introduce ArchTests instead of ArchRules
• 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