refactor(aggregator): move timeToExpiry task to config file

[MarcosNicolau]

Description

This pr moves the timeToExpiry time set when Initializing a new task in the aggregator to the config file and sets it to a week by default.

Testing

1. Setup a localtestnet with 1 operator.
2. Kill the operator
3. Sends proofs
4. Restart the operator after some time and you should expect the right behavior based on the value you provided in the config file.

Type of change

• Refactor

Checklist

• “Hotfix” to testnet, everything else to staging
• Linked to Github Issue
• This change depends on code or research by an external entity
  • Acknowledgements were updated to give credit
• Unit tests added
• This change requires new documentation.
  • Documentation has been added/updated.
• This change is an Optimization
  • Benchmarks added/run
• Has a known issue
  • Closeschore: change timeToExpiry parameter passed to blsAggregationService.InitializeNewTask #1207
• If your PR changes the Operator compatibility (Ex: Upgrade prover versions)
  • This PR adds compatibility for operator for both versions and do not change batcher/docs/examples
  • This PR updates batcher and docs/examples to the newer version. This requires the operator are already updated to be compatible

[JuArce]

Just a note. If we set a time too high for the task expiration (bls_service_task_timeout: 168h), we won't see the trace in the telemetry service until the task is expired because the trace is not closed