auto-injected constraint{} for signals should be sorted

[jippi]

Nomad version

v0.7.1

Issue

The order of auto-injected constraint{} for signal availability some times changes order, causing the job to be rolled / deployed / restarted when there are no functional different between the two.

it would be nice if the order in RTarget did not matter, as SIGHUP,SIGTERM and SIGTERM,SIGHUP are exactly the same

1. sort them before adding them automatically
2. make this generic and always split RTarget by , and sort them before evaluating the job

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.