Lay the groundwork for tag-based scheduling and add worker tags (#326)

This defines worker tags and adds them to worker-provided tagsets and task-required tagsets.

Scheduling can be tested, but it's off by default otherwise we break scheduling on not updated workers.

Once this is fully deployed on workers, we can use tags for scheduling, drop the equivalent information from task metadata, and likely drop can_run_on