Site defaults supporting multisite

[mwagena]

With this PR support is being added for multisite.
Fallback is added when using a config file with path to the yaml file.

output paths will be ./content/seo/sitehandle/defaults.yaml

Closes #289.

[duncanmcclean]

This PR still looks like it's a work-in-progress (lots of tests are failing & there's probably more to it than changing the file paths).

Going to mark this as a draft for now.

[mwagena]

hi @duncanmcclean
I'll have to look into the tests then, the change is doing it's work when i tested it out while saving the 'site defaults' from within statamic cp. Also it returns the right data in the html pages in for example the <title> tag.

[mwagena]

@duncanmcclean i have updated the code slightly to support older versions of Laravel, in my enthusiasm i forgot the config()->bool() and config()->string() methods were relatively new

[duncanmcclean]

The tests still seem to be failing, I'm afraid.

When this is ready for us to look at, feel free to mark it as "Ready for review".

[mwagena]

I have replaced the logic with regular php versions to support all Laravel versions, local tests ran OK.

[jesseleite]

Thanks @mwagena for your work on this! I actually have some in-progress stuff on this front, which handles schema, but I'm also working out the UI in the CP for localizable site defaults as well. Going to close this for now so that we don't introduce two ways of doing the same thing, but I wanted to say I appreciate your PR ❤️

[mwagena]

Thanks @mwagena for your work on this! I actually have some in-progress stuff on this front, which handles schema, but I'm also working out the UI in the CP for localizable site defaults as well. Going to close this for now so that we don't introduce two ways of doing the same thing, but I wanted to say I appreciate your PR ❤️

out of curiosity, what's the expectation on releasing this?