Change `name` scope in `scm` language to include the `@`

[pokey]

If I have the following code:

(aaa) |
(bbb) @ccc

(where | is my cursor), I want to be able to say "bring name cap", but that results in

(aaa) ccc
(bbb) @ccc

rather than the desired

(aaa) @ccc
(bbb) @ccc

I think we were trying to be too fancy. I'd be inclined to just include the @ in the name scope, and stop using @ as insertion delimiter

The drawback is we wouldn't get a @ when we say "pour name" or "change name"

Note that we could get something like this in the future where we'd support "bring name cap to this" if we had #1631, but that's still more verbose than "bring name cap"

If we decide to go this route, we should prob also include the . in "access" (#1519)

[pokey]

• "bring name air"
• "bring name air to bat"
• "bring name air to arg bat" (eg in (#foo! @bbb))
• "bring name air after bat"
• "pour name air"
• "drink name air"
• "chuck name air"
• "change name air"
• "leading name air" (really more interesting with "access")
• "copy name air" / "paste that" / "paste to name bat" / "paste after name bat"

[pokey]

Update from discussion:

• Include @ in content range
• Don't have @ be insertion delimiter

Note that this makes drink, pour, and change inconvenient due to missing @, but those are not that common in my current experience; let's implement this and see how painful it is

In the future, we may want to get fancy and include the @ and also use it as insertion delimiter but have it be smart so that it won't insert the @ if it's next to an @. Could do this with some kind of "soft" / "smart" query predicate operator

For "access",

• Make it private by not having it appear in csvs, but don't throw error if we manually add it to the csv. Also call it private.access
• Ship it as is where it includes the . in the content range