`completion.addColonsToModule` is always `true` for `crate`, `self` and `super`

completion.addColonsToModule controls ::-suffix-emitting only for module in a path, but doesn't control same behavior for crate, self and super — they always have the form of "token::". The crate/self/super is a special cases of the module.

Use-case, current behavior

Legend: <|> — cursor position, completions requested by ra ls.

• Call: cra<|>::module::thing(); — completion is always crate::, adds extra path-delimiter, it's a PITA to delete it every time;
• Attr: #[crat<|>::thing] — same as above
• Use: use crat<|>::* — same as above, we'll get use crate::::*

Expected behavior

Setting completion.addColonsToModule controls crate, self and super in same way as other mod- parts of a path.

So, for completion.addColonsToModule = false expected behavior is:

1. supe<|> and accepting super-completion, expected final result should be super;
2. supe<|>:: and accepting super-completion, expected final result should be super::;

rust-analyzer version: rust-analyzer 1.98.0-nightly (57d06900 2026-05-27)

rustc version: rustc 1.98.0-nightly (57d06900f 2026-05-27)

editor or extension: any (VSCode, Gram, Zed, etc..)

Start by tracing the completion.addColonsToModule handling for crate, self, and super, then reproduce the call, attribute, and use examples from the issue. Done means the setting controls whether these completions add ::, including the different results when the typed path already ends with ::.