testregistry incomplete/inconsistent data

[MarcCharlebois]

Describe the bug
testregistry incomplete and inconsistent data

To Reproduce
N/A

Expected behavior
N/A

Logs
N/A

Network device platform (please complete the following information):
N/A

Additional context
Looking at the proto for testregistry - there seem to be some inconsistencies with the current values populated and the proto. Please see below examples.

• Authz-1 Doesn't follow the the regex listed (not sure if the regex should be adapted to fit the tests more loosely, or if the test IDs should be restricted to the regex).
  

  featureprofiles/proto/testregistry.proto

  Lines 32 to 35 in f11401c

  	// id -- Test ID, required, must be unique, must match the regex:
  	// [A-Z][A-Z]+\-[0-9]+(\.[0-9]+)?
  	// Test ID should match the rundata.TestPlanID of the linked exec.
  	// For example: AA-1.1

  
  

  featureprofiles/testregistry.textproto

  Line 76 in f11401c

  id: "Authz-1"

• Certain test IDs are repeated in the description (shouldn't be necessary if the we already have the ID)

  featureprofiles/testregistry.textproto

  Lines 834 to 835 in f11401c

  	id: "RT-7.6"
  	description: "RT-7.6: BGP Link Bandwidth Community - Aggregation"

• Do we expect each test to be fully populated with Description, ID, Readme, Exec?

[dplore]

Yes, we want testregistry to provide an id, description and link to the relevant README.

I've created an internal tracking issue to add a CI check (and a generator for testregistry) to resolve these issues.