Don't show leading / trailing / removal / insertion delimiter if equal to token semantics in scope fixtures

[pokey]

I believe we'd just expand to containing token if scope type isn't token, and then check that its content range / leading / trailing / insertion delimiter / removal are equal the token scope. If so, we drop leading / trailing / insertion delimiter / removal. I don't think we have a way to expand to containing scope via generic scope provider, but trivial to add and prob useful for future visualizations, eg show scope containing cursor

See #2102 (comment) for more

[pokey]

update from meet-up:

• Let's not bother with this, because we want to capture full semantics
• Discussed just not defaulting to token removal / insertion semantics, but decided that it conflicted with Automatically try to remove scopes as if they're token, line, block, file if they have no removal behaviour #855 in the case where the scope equals a token range
• Let's start with Don't show lines in our facet tests that are outside of the range #2164, and hopefully that will shorten things enough that we won't need this issue