[Perf Tests] [AMQP] Test naming consistency update

[HarshaNalluru]

For consistent naming across languages

[azure-sdk]

API change check

API changes are not detected in this pull request.

[pvaneck]

Nit: On second thought, I feel like we should also have the -batch suffix here for a bit more clarity and consistency, especially since looking at the SB tests, we test both receive in batch/or non-batch form. In Python we have EH perf-tests for receive in batchs/non-batches, as well. Not a blocker, and ultimately doesn't matter too much, but WDYT?

[HarshaNalluru]

receive-queue-messages-batch in SB is different from receive-events here.

// receive-queue-messages-batch in SB
messages = await receiver.receiveMessages(...)
// (= Batch)

// receive-queue-messages in SB
// Alternative name: process-queue-messages
    receiver.subscribe(
      {
        processMessage: async (_message: ServiceBusReceivedMessage) => {
          .....
        },
        processError: async (args: ProcessErrorArgs) => {
          ....
        },
      }
    );

// receive-events in EH
// Alternative name: process-events-batch
    receiver.subscribe(
      {
        processEvents: async (events: ReceivedEventData[], _context: PartitionContext) => {
          // ..... events (= Batch)
        },
        processError: async (error: Error | MessagingError, _context: PartitionContext) => { 
          .....
        },
      }
    );

Adding batch to EH streaming might be misleading in the context of EH vs SB.

---

If you want to put "batch" in the name, I would prefer..

1. receive-queue-messages-batch in SB
2. process-queue-messages in SB
3. process-events-batch in EH

[pvaneck]

That works for me :)