Merge annotation-processor-test into annotation-processor

[alzimmermsft]

Description

Prototype merging annotation-processor-test into annotation-processor to contain both the processor and end-to-end testing code in the same package. This removes the need to indicate an annotation dependency anywhere and will ensure processing and testing are using the same processor version, limiting the possibility for breaking changes.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[azure-sdk]

API change check

APIView has identified API level changes in this PR and created following API reviews.

io.clientcore:annotation-processor

[JimSuplizio]

@alzimmermsft @srnagar @samvaity
Why is annotation-processor, which has multiple libraries, in a subdirectory of sdk\clientcore instead of being in an sdk\annotation-processor subdirectory?

[samvaity]

@alzimmermsft @srnagar @samvaity Why is annotation-processor, which has multiple libraries, in a subdirectory of sdk\clientcore instead of being in an sdk\annotation-processor subdirectory?

@JimSuplizio annotation-processor is a tooling package for clientcore and hence we wanted to retain it under clientcore grouping.