Add the blacklist reason to the blacklist file

[Po-Hsu Lin]

For the blacklist mechanism, we are just checking the file existence with the corresponding file name (kernel version / arch / series / flavour and etc)

I would like to encourage people to add the reason why we're having this blacklist file into the corresponding blacklist file.

It will be helpful for people to see why this is blacklisted instead of navigating through the git log.

Further more, we can make use of this content to print out the reason with jenkins job, making it become more self-explanatory for test report reviewers.

[Sean Feole (sfeole)]

I'm in agreement with this, and its a good idea. That means EVERYTHING in a-c-t is going to have to change. who is going to own that?

Perhaps we can make a trello card to track this rather than a launchpad bug?

[Sean Feole (sfeole)]

Trello card created, closing LP bug.