Add workspace rule for master layout orientation

[thejch]

Describe your PR, what does it fix/add?

Addresses #3174
No monitor rules but we can at least have a workspace rule

Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)

Not sure if this is ideal because this is only for master but it's in the general workspace rules.

Is it ready for merging, or does it need work?

Ready.

[vaxerski]

I'd do a similiar approach to dispatchers. layoutopt or something and then orientation top etc

[thejch]

I'd do a similiar approach to dispatchers. layoutopt or something and then orientation top etc

Changed it to layoutopt:orientation:top

[vaxerski]

for future-proofing the code it'd be better if it was a map str -> str, we might add more layoutopts later.

[thejch]

for future-proofing the code it'd be better if it was a map str -> str, we might add more layoutopts later.

added

[vaxerski]

lgtm, wiki mr needed though

[thejch]

Actually, str -> str is not the best idea since you can't store other types (bool, int, whatever may come in the future). I want to use str -> std::any for this, or even a struct, but I think std::any sounds easier to deal with atm. Thoughts?

[thejch]

Made some changes. Wiki MR added as well

[vaxerski]

lgtm