Allow non-maintainer GitHub accounts and false positive to be ignored

[RobertKielty]

For a Project, The MAINTAINER ROLL CALL page shows

• a list of maintainers PRESENT IN CNCF DATABASE

• the project's Legacy Maintainer File

• a list of GitHub accounts that maintainer-d sees are not in the DB, but are in the project's legacy roster file, NOT PRESENT ON CNCF DATABASE, sometimes the GitHub Accounts on this list do not truly represent actual active maintainers on the project and we should not add them to the database because they are:

  • GitHub accounts referenced in the legacy roster files that are shout outs to founders or early contributors
  • false positives arising out of maintainer-d attempting to infer GitHub accounts from the wide variety of proprietary and unstructured text that projects use to list out maintainer rosters.

False Positives of any kind on the NOT PRESENT ON CNCF DATABASE present data auditing challenges.

Althought possible to see false postives by reading the legacy files, looking at the list, comparing both and reasoning about why maintainer-d thought a GitHub Account should be considered for addition to the DB, after you go thru that investigation it would be best to cross out the false positive and record that human inference.

This feature request will allow a staff user to mark a maintainer as a false postitive so as to clear down the list that appears on the RHS of the Roll Call page.

This will then allow staff to work thru the legact roster files, auditing files' contents so that as the Roll of active maintainers is "called"

GIVEN that I am visiting the ROLL CALL page for a CNCF project as a Staff User,
WHEN maintainer references appear on the "NOT PRESENT ON CNCF DATABASE" list 
AND I can see that they are not a maintainer for whatever reason
THEN I need to be able to mark them a false positive to indicate that they
 should not be considered for addtion to the active roster of maintainers 
 for the Project 
and the NOT PRESENT ON CNCF DATABASE list can be cleared down to zero 
both during this visit and subsequent visits to the page