AMQP Perf Test Framework support (Batch and Event Processor APIs)

[g2vinay]

Adds Performance Testing Support for AMQP Batch and Event Processor APIs.

Restructured the Performance Framework in following manner:

• The Batch Perf Test class allows to add performance tests for batch APIs in AMQP and HTTP land, example batch receiving.

• The Event Perf Test class allows to add performance tests fpr Event Processor APIs in AMQP land, example Event Processor.

• Note, The class names do not have Stress in them, that is intentional, as these are not meant for Stress tests.

• The name of existing PerfStressTest class will also be renamed to remove Stress in a following PR.

Tests added to prove functionality:

Regression Tests:

No Op Test:

Concurrency	Type	Main	PR
1	async	2,293,753.76	2,215,610.77
32	async	7,171,413.84	7,343,269.63
1	sync	13,246,290.48	13,230,261.64
32	sync	39,063,083.17	39,441,495.25

Storage Download Blob Test:
Size: 10240 bytes.

Concurrency	Type	Main	PR
1	async	307.34	304.56
32	async	6,765	6,907

Functionality Tests:

Event Perf Test (MockEventProcessor):
Java Event Processors are all sync only.
Max Events Per Second: null

Concurrency	Type	Main (ops/s)
1	Sync	11,482,996.28

Batch Perf Test (Mock Batch Receiver)
Min Messages = 0;
Max Messages = 10;

Concurrency	Type	Main (ops/s)
1	Async	4,953,801.19
32	Async	14,939,589.71
1	sync	12,124,112.65
32	sync	16,845,403.99

[mikeharder]

Approved pending remaining comments.

[check-enforcer]

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run java - [service] - ci