Higher priority for "wrapping" symbols in `(Sub)?Word` navigation mode

Description

The main idea would be is to grant a higher priority to the quotes [`"']+ over other \W symbols. As they're used to wrap content up and it is important to respect their boundaries.

• "(?s)(?:some|ThInG).*$"
  Trying to delete/navigate through similar RegEx, it currently yoinks "(? and ).*$", but would be much preferable if it were split into " <= (? <= ... and ... => ).*$ => " respectively.

Optionally, and perhaps exclusively for the SubWord mode, can similar logic be applied to brackets, parentheses, or any other paired delimiters, that do not match its closing/opening pair?

Or in the "back-to-back" position ( e.g. )(, ],{ ), which is often the case with RegEx or nested data structures.

• [(),[],{}] or {[[()]]}
  These sequences would be wiped from any position to start/end, but when properly separated by \s characters [ (), [], {} ], { [ [ () ] ] } they are treated as expected.
  Could be useful when working with string formatting patterns ( e.g. f"Items: {[z,x.c,v]}", $"{}/{}/{}.{($ext)}" ), or building some poorly designed data structure

With SubWord mode being considered less hasty and more precise, perhaps it is a good idea? Then again, maybe it's just me whining, as the default navigation mode already does that, so no pressure here.

@masmu

Reproduce the quoted and back-to-back delimiter examples in (Sub)?Word navigation mode. The issue names no files, tests, or entry points, so first locate the navigation-mode implementation and existing tests; clarify whether quote priority, paired delimiters, or both are in scope, then define expected cursor and deletion boundaries before changing behavior.