tools.md: add bevry's automation tooling

[balupton]

close #5

/cc #114 #172 #280 #298 #299

[balupton]

In hindsight, I think tools.md should just be replaced by say a awesome-maintenance repo that follows in the awesome-* spirit. As otherwise good tooling may be left out because such tooling may not comply with the requirement of this working group's blessing.

[Eomm]

I would add a sentence to admit other good references

I like the awesome list format, but maybe it is too early and we should collect and include more data.
awsome requirements as ref

[ljharb]

why is this a standard we’re endorsing? I don’t think it’s appropriate for a node group to bless a particular community convention, even for an informational list.

[mhdawson]

I agree with @ljharb, the first line in the file says that these are tools built by the packaged maintenance team which the additional is not.

[wesleytodd]

TBQH, I think we should just delete this file until we have some clear purpose for it. I suspect we will never want it as it would give too much weight even on the tools we end up building and supporting.

[mhdawson]

I agree we should just delete the file.

[mhdawson]

Going close this out since we are going to remove the file anyway.