[5.x] Fix blueprint override logic

[jasonvarga]

While reviewing #9327 I noticed that there's some behavioral issues with how blueprint overrides work.

• When you have a custom namespace, and the vendor override directory exists (e.g. blueprints/vendor/custom), if the directory is empty, you see no blueprints at all. Not even ones that haven't been overridden.
• If there are any overrides in that directory, only they are shown. Non-overridden ones do not get displayed.
• If you have a yaml file in the override directory that doesn't exist in the regular directory, it gets shown. It shouldn't. You shouldn't be able to override a blueprint that doesn't exist. You're overriding, not adding. (Up for debate I guess, but it was ambiguous so I went with this.) Reverted in [5.x] Fix blueprint override logic, pt 2 #10668

[jasonvarga]

While reviewing #9327 I noticed that there's some behavioral issues with how blueprint overrides work.

• When you have a custom namespace, and the vendor override directory exists (e.g. blueprints/vendor/custom), if the directory is empty, you see no blueprints at all. Not even ones that haven't been overridden.
• If there are any overrides in that directory, only they are shown. Non-overridden ones do not get displayed.
• If you have a yaml file in the override directory that doesn't exist in the regular directory, it gets shown. It shouldn't. You shouldn't be able to override a blueprint that doesn't exist. You're overriding, not adding. (Up for debate I guess, but it was ambiguous so I went with this.) Reverted in [5.x] Fix blueprint override logic, pt 2 #10668

[jasonvarga]

While reviewing #9327 I noticed that there's some behavioral issues with how blueprint overrides work.

• When you have a custom namespace, and the vendor override directory exists (e.g. blueprints/vendor/custom), if the directory is empty, you see no blueprints at all. Not even ones that haven't been overridden.
• If there are any overrides in that directory, only they are shown. Non-overridden ones do not get displayed.
• If you have a yaml file in the override directory that doesn't exist in the regular directory, it gets shown. It shouldn't. You shouldn't be able to override a blueprint that doesn't exist. You're overriding, not adding. (Up for debate I guess, but it was ambiguous so I went with this.) Reverted in [5.x] Fix blueprint override logic, pt 2 #10668

[jasonvarga]

While reviewing #9327 I noticed that there's some behavioral issues with how blueprint overrides work.

• When you have a custom namespace, and the vendor override directory exists (e.g. blueprints/vendor/custom), if the directory is empty, you see no blueprints at all. Not even ones that haven't been overridden.
• If there are any overrides in that directory, only they are shown. Non-overridden ones do not get displayed.
• If you have a yaml file in the override directory that doesn't exist in the regular directory, it gets shown. It shouldn't. You shouldn't be able to override a blueprint that doesn't exist. You're overriding, not adding. (Up for debate I guess, but it was ambiguous so I went with this.) Reverted in [5.x] Fix blueprint override logic, pt 2 #10668

[jasonvarga]

While reviewing #9327 I noticed that there's some behavioral issues with how blueprint overrides work.

• When you have a custom namespace, and the vendor override directory exists (e.g. blueprints/vendor/custom), if the directory is empty, you see no blueprints at all. Not even ones that haven't been overridden.
• If there are any overrides in that directory, only they are shown. Non-overridden ones do not get displayed.
• If you have a yaml file in the override directory that doesn't exist in the regular directory, it gets shown. It shouldn't. You shouldn't be able to override a blueprint that doesn't exist. You're overriding, not adding. (Up for debate I guess, but it was ambiguous so I went with this.) Reverted in [5.x] Fix blueprint override logic, pt 2 #10668

[jasonvarga]

While reviewing #9327 I noticed that there's some behavioral issues with how blueprint overrides work.

• When you have a custom namespace, and the vendor override directory exists (e.g. blueprints/vendor/custom), if the directory is empty, you see no blueprints at all. Not even ones that haven't been overridden.
• If there are any overrides in that directory, only they are shown. Non-overridden ones do not get displayed.
• If you have a yaml file in the override directory that doesn't exist in the regular directory, it gets shown. It shouldn't. You shouldn't be able to override a blueprint that doesn't exist. You're overriding, not adding. (Up for debate I guess, but it was ambiguous so I went with this.) Reverted in [5.x] Fix blueprint override logic, pt 2 #10668

[jasonvarga]

While reviewing #9327 I noticed that there's some behavioral issues with how blueprint overrides work.

• When you have a custom namespace, and the vendor override directory exists (e.g. blueprints/vendor/custom), if the directory is empty, you see no blueprints at all. Not even ones that haven't been overridden.
• If there are any overrides in that directory, only they are shown. Non-overridden ones do not get displayed.
• If you have a yaml file in the override directory that doesn't exist in the regular directory, it gets shown. It shouldn't. You shouldn't be able to override a blueprint that doesn't exist. You're overriding, not adding. (Up for debate I guess, but it was ambiguous so I went with this.) Reverted in [5.x] Fix blueprint override logic, pt 2 #10668

[jasonvarga]

While reviewing #9327 I noticed that there's some behavioral issues with how blueprint overrides work.

• When you have a custom namespace, and the vendor override directory exists (e.g. blueprints/vendor/custom), if the directory is empty, you see no blueprints at all. Not even ones that haven't been overridden.
• If there are any overrides in that directory, only they are shown. Non-overridden ones do not get displayed.
• If you have a yaml file in the override directory that doesn't exist in the regular directory, it gets shown. It shouldn't. You shouldn't be able to override a blueprint that doesn't exist. You're overriding, not adding. (Up for debate I guess, but it was ambiguous so I went with this.) Reverted in [5.x] Fix blueprint override logic, pt 2 #10668