Change interior scope handler priority to favor surrounding pair interiors

[AndreasArvidsson]

Fixes #3067

[pokey]

This seems wrong to
me. I would argue lang scope should take precedence over generic text scope. Why are we even matching lang scope here?

That being said, I'm not going to get in the way of merging to get the unit test in and filing an issue to follow up and understand what's going on

[AndreasArvidsson]

We do have a sorting algorithm based based on the domain. I don't think it matters to much to the us sir how the scope is implemented. For example why would string be down prioritize compared to other scopes?

It also makes sense to have the new order since we know that if the domain of a surrounding pair interior is always larger than the content range. Until we find an actual use case that doesn't work I think this solution is actually quite decent.