Still load legacy config if it exists instead of failing

[cmcfarlen]

Everything is broken and I'm not prepared for records.yaml

[DoingTheNeedful]

Thanks, @cmcfarlen - swapping from a format that's been in use for years to yaml necessitates a change of a ton of tooling. The prior change would have been breaking for just about every org that uses ATS, with a significant investment in trying to change every part of build, validation, and config management. Even if you believe that swapping to yaml would be better, you cannot expect that to be a minor change.

[brbzull0]

Why removing this?? In any case we can just:

Test.SkipIf(Condition.true("..."))

[brbzull0]

We have already talked about this on slack but just for the record:
As discussed(dev and user mailing list) before, we agreed to have single parsing and fail if the legacy file is found. As also requested, a tool is provided for the translation with a guide on how to move on.
I have no issues with having it dual but just making sure that we are all on the same page.

If there is anything I can do to make the process easy just let me know and I'll do it.

[brbzull0]

I've created an issue to track a solution for this, regardless of what we do with this.

#9384

[bryancall]

We talked about this in the PR/issue scrub and would like to have a discussion at next weeks PR/issue scrub. A final decision should go to the mailing list. Marking it as a draft, so it doesn't get merged in before we discuss.

[cmcfarlen]

I'm going to close this and we can work on the yaml support around tooling instead.