[Bug]: In Job, if executable is found locally, it is always added to the sandbox

[maxnoe]

Search before creating an issue

• I have searched existing issues and confirmed this is not a duplicate

Bug Description

In the Job.setExecutable, the executable is always uploaded to the job sandbox:

DIRAC/src/DIRAC/Interfaces/API/Job.py

Lines 126 to 132 in b0bc9cf

	if os.path.exists(executable):
	self.log.verbose(f"Found script executable file {executable}")
	self.addToInputSandbox.append(executable)
	logName = f"{os.path.basename(executable)}.log"
	else:
	self.log.warn("The executable code could not be found locally")
	logName = "CodeOutput.log"

This happens even if e.g. the executable is a path on cvmfs

Steps to Reproduce

On a host that has cvmfs available:

job = Job()
job.setExecutable("/cvmfs/<some repo>/<some executable>")

Expected Behavior

The executable is assumed to be available on the worker node because it's a path on CVMFS

Actual Behavior

The executable is added to the sandbox.

Environment

No response

Relevant Log Output

Additional Context

No response

[aldbr]

We can add a flag include-in-sandbox=False to avoid that (in the Job API),
We don't want to break the current API as people might rely on it.