Update manual.csv for TD, document pipeline

[mmccool]

• Changes in assertions in TD1.1 change some of the assertions and/or ids, i.e. IANA -> security
• Current manual.csv in wot-testing is old
• Need to update manual.csv to reflect this
• Some pipelines issues; how and when do we update the AssertionTester, Implementation Report, etc? Need to document process. Can this be automated, e.g. using Toumura-san's script to extract assertions, then AssertionTester subtracts the ones that are testable, generating a new manual.csv, etc...

[egekorkan]

The problem is to make sure that this pipeline works as autonomously and quickly as possible

1. Change happens in the TD spec that affects an assertion (new, deleted, update)
2. Assertion tester does not implement this assertion currently, so it is flagged as manual by doing a difference between the whole list of assertions and the automatic ones.
3. This new manual.csv should be submitted to this repository
4. Every implementation owner should update their implementation to reflect that