Support for setting maxPSS in specified tasks (Merge tasks)

[LinaresToine]

Impact of the new feature WMAgent

Is your feature request related to a problem? Please describe. Express Merge jobs require more than the default 2.3 GiB defined in addRuntimeMonitors. The current memory setting functions ignore "Merge" tasks, which prevents them to ever have more than 2.3 GiB maxPSS.

• setJobResourceInformation
• setMaxPSS

Describe the solution you'd like We want to be able to set an arbitrary value of maxPSS only for Express Merge tasks, or for that matter, any specified task. Currently, a workload goes through all its tasks and if its not "Merge", "Cleanup" or "LogCollect", it will set it with the same maxPSS value. We want to discriminate among tasks so that we can have "Merge" tasks with a maxPSS value of our choice without affecting the maxPSS value of other tasks within the workload.

Describe alternatives you've considered I have considered giving flexibility to the current memory setting functions so that if a task is specified then there is no need to ignore it if it happens to be type "Merge". Also, adding a "TaskMemory" parameter support in company of the current "Memory" parameter in updateArguments. This is explicitly visible in modified updateArguments

Such changes can be seen in the patch: https://github.com/dmwm/WMCore/pull/12085

Additional context None