Remote Taskfiles: add a new trust mechanism

[maciej-lech]

Description

Hey!

This is a follow-up of my comment here: #1317 (comment)

In a Remote Taskfiles experiment , I would like to propose adding a new --trust CLI flag and remote.trust configuration option.

Currently, when using remote taskfiles, one is asked for a confirmation. This new flag/setting will bypass that.

This is different than --yes, because:

1. It can be configured in taskrc
2. It doesn't answer yes for all prompts

Example case

1. I have a quite large system, structured in a modular way, with many taskfiles.
2. I have some generic taskfiles placed in a separate git repository, so they can be reused in many places.
3. I trust that generic taskfiles - they are managed by the same team of people.
4. If I was care about preventing supply chain attack, which I am not really, I could use checksum feature
5. I don't want to force people to answer yes or add --yes to every invocations, especially as there are some potentially destructive tasks protected with additional prompt so --yes may be dangerous, when used without thinking
6. Certainly, I don't want to add --yes to my CI/CD pipelines (read previous point)

[maciej-lech]

As oposie of having --trust/remote.trust as a simple bool flag, it could take a list of trusty hosts. And be empty be default, so this feature is fully backward compatible.