feat: add configurable retry with exponential backoff for RemoteDisconnect errors

[nicolasbisurgi]

Summary of changes

• Add configurable exponential backoff for RemoteDisconnect retry handling
• Add configurable exponential backoff for async operation polling
• Preserve default behavior for backward compatibility
• Update RestService tests

New Parameters to support the changes

RemoteDisconnect Retry

Parameter	Default	Description
remote_disconnect_max_retries	5	Max retry attempts
remote_disconnect_retry_delay	1.0s	Initial delay
remote_disconnect_max_delay	30s	Maximum delay cap
remote_disconnect_backoff_factor	2	Backoff multiplier

Example using default parameters

Retry	Delay
1	1s
2	2s
3	4s
4	8s
5	16s

This strategy:

• Reduces load on the TM1 server when it's recovering
• Gives transient network issues more time to resolve
• Adapts to varying network conditions between client and server

Async Polling

Parameter	Default	Description
async_polling_initial_delay	0.1s	Initial poll delay
async_polling_max_delay	1.0s	Max delay cap
async_polling_backoff_factor	2	Backoff multiplier

Backward Compatibility

Default parameters preserve existing behavior:

• Async polling caps at 1s (same as before)
• Both features use capped exponential backoff to prevent unbounded delays.

[MariusWirtz]

Good enhancement! Thank you @nicolasbisurgi

I have two small change requests

• Please squash the commits into 1 commit before we merge
• Please also list the new arguments in the docstring of the TM1Service constructor (because most people interact with the RestService only indirectly)