Buildstream fails to spot bad project.conf

Summary

Some mal formed project.conf files cause bst to think there is no project and ask if you want to make a new one. but if you decline they then tell you about your project.conf file being bad.

Steps to reproduce

I don't have a minimal reproducible test but something like this https://gitlab.com/pointswaves/bootable-images/blob/bug/project.conf#L23 should be able to be simplified to a test case.

What is the current bug behavior?

bst should report the issue with the project.conf and not think there is no porject

What is the expected correct behavior?

report a problem with the project.conf

---