Switch from the v1 Outlet to the v2 PipelineClient

Co-authored-by: Tiago Queiroz <[email protected]>

I don't wanna use `time.Sleep`, this is just a test.

Trying to listen for the ack of the last event, and store its
checkpoint information

Alongside the partition ID, users can optional send event with a
partition key.

Add an (optional) partition key to the event hub metadata.

The new migrate_checkpoint config option controls if the input v2
should perform a migration check on start.

If migrate_checkpoint is true, the input checks and performs the
migration (if v1 info exists) on the very first v2 run.

If migrate_checkpoint is false, the input will skip the migration
assistant and will not perform any checks or migration.

Expand processor options by adding a new `start_position`
configuration.

Possible values for `start_position` are:

- "earliest" to start from the beginning of the event hub retention
  period.
- "latest" to start from new events.

The input uses the 'start_position' option when checkpoint information
from the storage account container is unavailable (on the input's
first start).

Makes the receive configuration settings available for customization
on the input settings.

The current default values (receive_timeout: 5s, receive_count: 100)
are probably fine, but it is better to make these options available
to users.

Co-authored-by: Andrew Gizas <[email protected]>
Co-authored-by: subham sarkar <[email protected]>

Also update the option description as well adding the default value.

It's better to check the private data in the event has the expected
type.

Adding more details to the message logged on successful store:

- sequence_number
- offset
- enqueued_time

The teardown() function is responsible to release all the resources
allocated in the setup() function.