Change connector partition name on restart

[Kerkesni]

The partition name is used as an indicator in the offsets topic to distinguish between resume tokens of the different connectors.

When a connector is respawned it should start processing event from the current moment and not use the previous resume token as it can be invalid if the connector stayed shut for a long time and the mongo oplog rotated.

Issue: BB-463

[bert-e]

Hello kerkesni,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Status report is not available.

[bert-e]

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

[Kerkesni]

/approve

[bert-e]

Integration data created

I have created the integration data for the additional destination branches.

• this pull request will merge bugfix/BB-463-change-connector-partition-name-on-restart into
  development/8.6
• w/8.7/bugfix/BB-463-change-connector-partition-name-on-restart will be merged into development/8.7

The following branches will NOT be impacted:

• development/7.10
• development/7.4
• development/7.70
• development/8.5

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: approve

[bert-e]

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

• ✔️ development/8.6

• ✔️ development/8.7

The following branches will NOT be impacted:

• development/7.10
• development/7.4
• development/7.70
• development/8.5

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

• Any commit you add on the source branch will trigger a new cycle after the
  current queue is merged.
• Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

[bert-e]

I have successfully merged the changeset of this pull request
into targetted development branches:

• ✔️ development/8.6

• ✔️ development/8.7

The following branches have NOT changed:

• development/7.10
• development/7.4
• development/7.70
• development/8.5

Please check the status of the associated issue BB-463.

Goodbye kerkesni.