[FEAT] Add rebatch feature

[Augustinio]

Description

• Added rebatch for closed batches
• Added unit tests
• Added parent_id on batch and job
• Updated documentation and changelog

Remaining Tasks

• e2es

Checklist

• The title of the PR follows the right format: [{Label}] {Short Message}. Label examples: IMPROVEMENT, FIX, REFACTORING... Short message is about what your PR changes.

Versioning (PASQAL developers only)

• Update the version of pasqal-cloud in _version.py following the changes in your PR and by using semantic versioning.

Documentation

• Update CHANGELOG.md with a description explaining briefly the changes to the users.

Tests

• Unit tests have been added or adjusted.
• Tests were run locally.

Internal tests pipeline (PASQAL developers only)

• Update and run the internal tests while targeting the branch of this PR.
  If your PR hasn't changed any functionality, it still needs to be validated against internal tests.

After updating the version (PASQAL developers only)

• Open a PR on the internal tests that updates the version used for the pasqal-cloud backward compatibility tests.

[Mildophin]

Good to me, few non blocking comments

[awennersteen]

Nice feature. LGTM

Feature request that might be out of scope:

Could we have a retry argument to the original batch submission?
We have some internal code in quantum libs that could be removed if it was possible to ask for automatic rebatching.

[Augustinio]

Nice feature. LGTM

Feature request that might be out of scope:

Could we have a retry argument to the original batch submission? We have some internal code in quantum libs that could be removed if it was possible to ask for automatic rebatching.

I think that would definitely be a separate issue/question @MatthieuMoreau0