fix(ruleset): rename rule to oas3-examples-value-or-externalValue

[nulltoken]

And update the description to better reflect the targeted field

Given that #1059 will already impact the user experience with regards to the ruleset, let's get all in an give that rule a more meaningful name.

Checklist

• Tests added / updated
• Docs added / updated

Does this PR introduce a breaking change?

• Yes
• No (From the API standpoint)

This results in a change in the OAS3 ruleset content (one rule removed and one rule added).

⚠️ This will impact users who tweaked the rule severity or silenced it

[philsturgeon]

Is this pressing? It can cause breaking changes for people: e.g: If anyone is skipping rules and we rename the rule, they've got a breaking CI.

If its just "this name is not entirely correct" then maybe we can save it for 6.0?

[nulltoken]

Is this pressing? It can cause breaking changes for people: e.g: If anyone is skipping rules and we rename the rule, they've got a breaking CI.

@philsturgeon Will #1059 already in, people will already suffer from this. The idea was to push forward and give the rule a proper name.

With #1059 only:
example-value-or-externalValue -> oas3-example-value-or-externalValue

With #1059 and this one:
example-value-or-externalValue -> oas3-examples-value-or-externalValue

[nulltoken]

@philsturgeon Or, I could revive the old rule along with the newly renamed one. Marking the old one as deprecated in the documentation. And log an issue to kill it for 6.0.

Thoughts?

[philsturgeon]

ahh ok I see! Yeah go ahead.

[nulltoken]

@P0lip @philsturgeon If both of you agree with the currently proposed changes, could this one get merged, please?

[philsturgeon]

Thank you!