Eliminate redundancy with example policy rules

[fviernau]

Both repositories, ort and ort-config currently contain example policy rules. In fact the ort-config ones have initially been created based on ORT's one and then extended. So, it's currently not clear what the right place for examples rules is.

Fix this as follows:

• The place for real world examples from now on should be ort-config repository
• ORT's example policy rules should be moved from examples to functional test assets and be minimized to avoid redundant testing

As a future follow-up (out of scope here) it seems reasonable to add a test which verifies that the rules in ort-config do compile / execute successfully.

[sschuberth]

• The place for real world examples from now on should be ort-config repository

I've given this some though again: I believe it would generally be nice if one could simply clone the ort-config repo to ~/.ort/config and work with it. This is already possible right now (pending this layout fix), but then ~/.ort/config also contains several files / directories that are not used as part of ORT's configuration at all, like the evaluator-rules, notice and notifications directories etc. While that doesn't hurt ORT's operation, it's unclean, and personally I'd prefer to move stuff that's not used as part of ORT's configuration to somewhere else; at least to a subdirectory, but maybe even a different repository, like ort-examples.