Allow PHP Blueprint Definitions

One can create php based blueprints in plugins but currently the autoloaded files from the core folders like site/blueprints only support yaml files.

I would love to create blueprints there with php as well (again, since it was possible in K2).

this is also related to my attepts to create PHP class based blueprints: https://github.com/bnomei/kirby-blueprints

reading either php or yaml is simple enough
$blueprints[$key] = require_once $path;
or in
yaml $blueprints[$key] = Yaml::read($path);

and the issue of having both a php and yaml file with the same name is just a plain user error.

this would also allow a visual bluepprint editor #20 to write/read php files to these folders allowing for better typehinting.

A strong typed way (with IDE-autocomplete and static analysis) for Blueprints would be great for anyone coming from a contemporary PHP point of view. (But avoid the chaos, that Symfony introduced by endorsing PHP config builders and deprecating them after a few years, as it turned out that they don’t cover all usecases. Now they switched to an array-shape backed PHP-Config-Array solution.)