LS: Add hovers for path segments

[integraledelebesgue]

Closes #6540

Changes:

• Modules appearing in paths have proper hovers containing information about their location
• Hovers look exactly the same as in Rust Analyzer

[reviewable-StarkWare]

This change is 

[piotmag769]

Reviewed 5 of 5 files at r1, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @Arcticae, @Draggu, @integraledelebesgue, @mkaput, and @orizi)

---

crates/cairo-lang-language-server/src/lang/inspect/defs.rs line 330 at r1 (raw file):

    /// Gets the module's documentation if it's available.
    pub fn documentation(&self) -> Option<String> {
        // Modules cannot have docstrings at the moment.

This is not true, get_item_documentation should deal with it

[mkaput]

Reviewed 5 of 5 files at r1, all commit messages.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @Arcticae, @Draggu, @integraledelebesgue, and @orizi)

---

crates/cairo-lang-language-server/src/lang/inspect/defs.rs line 313 at r1 (raw file):

                Some(stripped_path) => stripped_path.to_owned(),
                None => full_path,
            };

this is parent module full path. term full path as used here is very misleading

Code quote:

        let full_path =
            match full_path.strip_suffix(name.as_str()).and_then(|path| path.strip_suffix("::")) {
                Some(stripped_path) => stripped_path.to_owned(),
                None => full_path,
            };

[integraledelebesgue]

Reviewable status: 1 of 5 files reviewed, 2 unresolved discussions (waiting on @Arcticae, @Draggu, @mkaput, @orizi, and @piotmag769)

---

crates/cairo-lang-language-server/src/lang/inspect/defs.rs line 313 at r1 (raw file):

Previously, mkaput (Marek Kaput) wrote…

this is parent module full path. term full path as used here is very misleading

I rebuilt the path logic a bit and also changed those confusing names

---

crates/cairo-lang-language-server/src/lang/inspect/defs.rs line 330 at r1 (raw file):

Previously, piotmag769 (Piotr Magiera) wrote…

This is not true, get_item_documentation should deal with it

You're right. I added a proper decumentation retrieval logic

[mkaput]

Reviewed 4 of 4 files at r2, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @Arcticae, @Draggu, @orizi, and @piotmag769)

[mkaput]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @Arcticae, @Draggu, @orizi, and @piotmag769)

[piotmag769]

Reviewed 4 of 4 files at r2, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @Arcticae, @Draggu, @integraledelebesgue, and @orizi)

---

crates/cairo-lang-language-server/src/lang/inspect/defs.rs line 101 at r2 (raw file):

            }

            ResolvedItem::Generic(ResolvedGenericItem::Module(id)) => {

Out of curiosity: when do we enter each branch? What is a generic module? ;p

[integraledelebesgue]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @Arcticae, @Draggu, @orizi, and @piotmag769)

---

crates/cairo-lang-language-server/src/lang/inspect/defs.rs line 101 at r2 (raw file):

Previously, piotmag769 (Piotr Magiera) wrote…

Out of curiosity: when do we enter each branch? What is a generic module? ;p

I have no idea which semantic construct it corresponds to tbh. I just separated all branches somehow related to modules :)

[mkaput]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @Arcticae, @Draggu, @orizi, and @piotmag769)