KEP validation seems to be brittle?

[BenTheElder]

Verifying verify-kep-metadata.sh
--- FAIL: TestValidation (0.09s)
    --- FAIL: TestValidation/../../keps/sig-testing/2464-kubetest2-ci-migration/kep.yaml (0.00s)
        main_test.go:90: ../../keps/sig-testing/2464-kubetest2-ci-migration/kep.yaml has an error: error validating KEP metadata: "prr-approvers" must be one of (deads2k,johnbelamaric,wojtek-t) but it is a string: TBD

Fails on: #2465
But not on: #2420 related PRs.

IMHO this should not fail for provisional KEPs either, it seems reasonable to introduce a KEP provisionally before seeking PRR (not to mention #2311 / PRR should probably not apply to process etc. KEPs that do not target production in any way)

/kind bug

(Part of #2348.)

[BenTheElder]

assigning per

enhancements/OWNERS_ALIASES

Lines 179 to 183 in e9b84b1

	kep-tools-approvers:
	- jeremyrickard
	- johnbelamaric
	- justaugustus
	- mrbobbytables

[jeremyrickard]

@BenTheElder thank you for opening this, and I agree with you.

There is some work in flight to refactor much of this stuff, that we are planning to land after enhancement freeze. We'll circle back and review this issue against that and make some additional adjustments to the overall validation as we work through that.

[BenTheElder]

It turns out if it fails to find / parse the file it will just pass :-)
so having kep.yml instead of kep.yaml makes your implementable kep bypass PRR 🙃