Do not unset ARGS_EXTRA_PROCESS_o2_ctf_reader_workflow

[shahor02]

As it prevents passing extra options, like the limit on the N TFs to process

[github-actions]

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1
async-2024-PbPb-apass2
async-2023-PbPb-apass5

[chiarazampolli]

Mmm... Setting the max number of TFs always worked for me locally.

[shahor02]

Setting --max-tf <N> will work because the dpl-workflow.sh has a dedicated env.var. for that. But more selective options, like --max-tf-per-file N or --select-ctf-ids <CSL> will not. There is simply no reason to unset the env.var.

We should also eventually remove any option for the TF injection delay, as now all workflows support throttling.