Pasqal-cloud

Fixed

- Fixed bug when using a custom TokenProvider to authenticate to Pasqal Cloud Services

Changed

- Reorder documentation for clarity
- Clarify instructions to use a custom token provider for authentication

Changed

- Package renamed from **pasqal-sdk** to **pasqal-cloud**
- Import name renamed from **sdk** to **pasqal_cloud** (import sdk is now deprecated but still usable)

Changed

- `device_type` argument replace by `emulator` in sdk create_batch
- `DeviceType` replaced with `EmulatorType`

Deleted

- QPU device type and related logic

Added

- Added tests to check the login behavior.
- Added tests to check the override Endpoints behavior.

Changed

- The authentication now directly connects to the Auth0 platform instead of connecting through PasqalCloud.
- Small refactor of files, with the authentication modules in the `authentication.py` file, instead of `client.py`.

Deleted

- Account endpoint, we now use Auth0.

Changed

- Added a get_device_specs_dict function to the sdk
- Updated Readme for the device specs

Changed

- The default values for the tensor network emulator were updated to better ones.
- the client_id and client_secret was leftover in the Client object even though they are no longer used.
- Updated the README to also supply the group_id which is mandatory.
- Updated the default endpoint to `/core-fast` in accordance with infra changes. All users should use `/core-fast` in all environments.
- The PCS APIs Client was refactored to accept any custom token provider for authentication. This can be used by users as an alternative to the username/password-based token provider.