Remove automation teams and archive the automation repo #488

As explained in nodejs/Release#547 (comment)

Yes, so far I think most automation projects are maintained by individuals who have access and the commit access is not granted with teams - automation-collaborators is more like "TSC/TSC emeritus who also spend time on automation" (then they already have commit access to these repos anyway), rather than "automation team members who are given commit access to these repos".

Also based on the activity of automation team, I think it probably makes more sense to disband it now in favor of smaller teams for individual projects. We don't have meetings over there, the gitter channel is not active, and a lot of the work done in the automation projects are by Node.js collaborators who are not in that team anyway.

The automation team was created so that we can ping a group of people for work/reviews/ideas about automation, but it is too big and rarely used at this point. Instead we tend to just open issues/PRs in https://github.com/nodejs/node-core-utils (which is somewhat like a mono repo now where new tools are being added) where the we talk about more concrete ideas and work on actual code.

I think it's time to remove the following teams

• @nodejs/automation
• @nodejs/automation-admins
• @nodejs/automation-collaborators

And just assign collaborators to different projects when necessary - or when the team grows big enough, create teams for each project. So in addition I propose to create

• @nodejs/node-core-utils

To manage https://github.com/nodejs/node-core-utils

In addition I think it's also time to archive https://github.com/nodejs/automation - it was good for what we tried to do back then but now most of the activities happen in node-core-utils.

cc @nodejs/tsc