Style Parser : Change the default key message to detail which keys need changing

[KieronFerrey]

Pull Request Template

Description

Included the object keys that violated the test in the warning message to easily understand what needs changing.

Type of Change

Please delete options that are not relevant, and select all options that apply.

• ✅ Documentation

How have you tested this?

Tested using a style that violated the test, tested against a default style with no keys, one and two all of which behaved correctly.

Testing Checklist

Please delete options that are not relevant, and select all options that apply.

• ✅ Existing Tests still pass
• ✅ Ran locally on my machine

Code Quality Checklist

Please delete options that are not relevant, and select all options that apply.

• ✅ My code follows the guidelines of XYZ
• ✅ My code has been commented
• ✅ Documentation has been updated
• ✅ New and existing unit tests pass locally with my changes
• ✅ Main has been merged into this PR

[simon-leech]

I actually think we should update the styleparser tests with this change too, while we are here!

[RobAndrewHurst]

Putting into draft until tests are updated

[RobAndrewHurst]

@simon-leech @KieronFerrey

I have fixed the two hover and label tests to better suite the actual logic of the module. There is still an issue where the bogus key is not being removed from the style object. Let me know if you have any ideas.

[simon-leech]

Closed as this PR has the same change in - #1331