Proposal: disable auto-discovery of config file for deno run <remote entrypoint>

[kt3k]

If the users have custom typescript settings which are incompatible with default settings (e.g. frontend typings), they will see type errors when they execute the remote Deno scripts.

For example, a user develops frontend lib. deno.json has frontend types (e.g. "lib": ["dom", "esnext"], etc). When they want to run, for example, udd command in the CI, the command throws type error because of the incompatible type settings of the auto-discovered deno.json. (This happens, for example, in hayd/deno-udd#59, and they avoid the error by removing deno.json in CI UltiRequiem/timero@56dc4ba . This doesn't look great.)

This situation doesn't make sense because deno.json is usually only for local scripts. The config is not intended to be applied to all deno programs.

So I suggest we should disable auto-discovery of config file when the command is deno run <remote entrypoint>, which fixes the above situation.