Is your feature request related to a problem? Please describe.

riseOnHover may not be useful to some users, depending on their input mechanism.

Describe the solution you'd like

An option to accommodate everyone: riseOnInteraction (or riseOnHoverOrFocus), that would take effect on focus as well as hover.

• Ideally it'd simply replace riseOnHover, though that's a breaking change. Alternatively phase out riseOnHover gradually.
• Consider enabling by default (since the user is interacting with the marker, it's in their interest to also see it).

Describe alternatives you've considered

1. Change riseOnHover to also take effect on focus.
   I think this would then not be considered a breaking change, but the name wouldn't be accurate.

2. A riseOnFocus option, separate but related to riseOnHover.
   This would most likely cause developers to only enable one or the other, which would be unfortunate.

Additional context

Relevant Success Criteria: 2.1.1 Keyboard, 2.5.6 Concurrent Input Mechanisms.