Support `single_dep` and `multi_dep` functionality

[ahal]

The multi_dep and single_dep loaders (and related transforms) are some of the most widely copied Taskgraph logic from project to project. We've mentioned upstreaming this into Taskgraph countless times! However, over the years I've come to realize that this loader is unnecessary and overly complicated (most recently while working on mozilla-releng/mozilla-taskgraph#7 in conjunction with the linked firefox-android PR).

Essentially it's doing too much at once, building upstream artifacts, copying attributes, resolving keys. The root issue is that it adds a lot of complexity right up front, which every later transform then needs to deal with. Instead we should add complexity little by little, and only as needed.

I'm still formulating thoughts here, but I think my rough plan is to:

1. Add transforms for adding dependencies given a set of kinds.
2. Add a utility file for deriving upstream-artifacts from a task's dependencies.
3. Add transforms for copying attributes from a primary-dep.
4. Push more logic into the scriptworker payload builders.

I believe with the above pieces, we'll be able to completely obsolete the single_dep and multi_dep loaders and replace it with a much simpler and easy to follow setup.

[bhearsum]

Maybe you omitted it because it's fairly trivial to deal with in transforms already, and we may not need or want a generic method, but just for the sake of completeness I'll note that the other major thing that multi_dep does is handles chunking and fanning out tasks (eg: by locale, partner repack, et. al). The new split_by_locale transform in Gecko is an example of how to do this in transforms.

[ahal]

Ah yes, good call out!