fix: Add macro modifier for highlighting tokens in macro calls

[Veykril]

Followup to #14777 we have to tell the client about the semantic tokens inside macro calls as those can be remapped. Adding a modifier will force this behavior.

[Veykril]

@bors r+

[bors]

📌 Commit 8e11685 has been approved by Veykril

It is now in the queue for this repository.

[bors]

⌛ Testing commit 8e11685 with merge e9f9bc2...

[bors]

☀️ Test successful - checks-actions
Approved by: Veykril
Pushing e9f9bc2 to master...

[oxalica]

This breaks my coc.nvim setup and it displays everything inside macro invocation as CocSemMacro highlighting, which is intended to highlight the macro itself. The issue is that the token modifier name macro collides with token type name macro. coc.nvim prefers modifiers against types, and it successfully found the highlighting for modifier macro defined as CocSemMacro (through it's originally for the type macro), thus it gets used always.

The solution could be:

1. Define each type-modifier pair manually to override each back. This is tedious and impractical.
2. Remove CocSemMacro highlighting definition, so it fallback to highlighting of token types. But I'll lose highlighting for macro itself foo!.
3. Ask coc.nvim to use different highlighting groups to define colors of types and modifiers.
4. Ask rust-analyzer to use a different name for types and modifiers.

I'm not quite sure on which side this should be fixed.

[Veykril]

That sounds like a client bug to me. The client should not consider token types and token modifiers to be the same concept. They are very much separate entities.