Run FIDO2 conformance self-validation and remediate findings

[Bccorb]

Part of #155. Session 6. Depends on #171.

Problem

Once the conformance interface exists, the FIDO2 conformance test tools need to be
run and whatever they surface needs fixing. This analysis predicted the gaps it
could see from the code, but the tools will find things it could not.

Process notes, which matter for scheduling

• Tool access comes with registration on the FIDO Alliance certification site
• Self-validation results must reach the Certification Secretariat at least 14
  days before an interoperability event
• Interoperability testing, at a proctored event or on demand, must happen within
  90 days of a successful self-validation

Do not start the 90 day clock until the rest of this plan has landed. Register
for tool access early so the tools can be run iteratively, but treat successful
self-validation as the trigger for scheduling interop, not as a milestone to rush.

What to do

• Register for conformance tool access
• Run the tools, fix findings, repeat
• Once clean, submit self-validation results
• Schedule interoperability testing within the window

Acceptance

• A clean conformance run
• Self-validation submitted and acknowledged

Freeze status

FIDO conformance self-validation (exception 3). This is the item the whole FIDO
track exists to reach.