Prioritize Runtime Plugins based on alphabetic ordering of location paths

[amoertlseder]

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue).
• [x ] New feature (non-breaking change which adds functionality).
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
• [ ] Performance improvement
• [ ] Refactoring (so no functional change)
• [ ] Other (docs, build config, etc)

Checklist:

• [x ] I've added tests for my code. (most of the time mandatory)
• [x ] I have added an entry to the changelog. (mandatory)
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.

[amoertlseder]

Reason for this change: a plugin might depend on another plugin being initialized, e.g. in order to replace the logger and forward to previously installed logger.

[bollhals]

This would certainly help us. Making it deterministic prevents differences in different environments (e.g. Windows vs Linux)