fix remote resource check TPV rule and enable it

[sanjaysrikakulam]

This rule now handles "None" case as well.

Question:
Should we fail the job when the remote resource the user selects (even unconsciously (the presence of old tags in DB and the user forgot about it, and they have not changed it to the currently existing ones)) does not exist or tackle it in TPV and let it go to default?

[kysrpex]

Should we fail the job when the remote resource the user selects (even unconsciously (the presence of old tags in DB and the user forgot about it, and they have not changed it to the currently existing ones)) does not exist or tackle it in TPV and let it go to default?

Yes, I think we should fail it. If the user expects the job to go to a specific destination and it turns out it goes somewhere else then they may go crazy.

Take this hypothetical example: I send my jobs to a Pulsar cluster where there are GPU machines with 128GB of RAM. The Pulsar cluster is decommissioned at some point (removed from the list of available destinations), and I send a job that needs 100GB of RAM. If we do not fail the job with the rule from this PR, the user will just get an error telling them that there was no destination available to run the job (because we do not have GPU machines with that much RAM on EU), but they will not know the underlying reason.