fix(parser): clarify consecutive comparison diagnostics

[AaronAjose]

Clarify E1028 for consecutive comparison operators by adding conditionalguidance for chained comparisons and possible missing :: in generic paths, and update parser/semantic diagnostic test data with an additional 1 == 1 == 1 case.

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

[reviewable-StarkWare]

This change is 

[orizi]

@orizi made 1 comment.
Reviewable status: 0 of 4 files reviewed, 1 unresolved discussion (waiting on AaronAjose).

---

crates/cairo-lang-parser/src/diagnostic.rs line 225 at r1 (raw file):

            ParserDiagnosticKind::ConsecutiveMathOperators { first_op, second_op } => {
                format!(
                    "Consecutive comparison operators are not allowed: {} followed by {}. If this \

since you are separating cases - the comment should probably be actually based on the operator.
otherwise just much more messy with no benefit.

[AaronAjose]

@orizi Done, please re-check, thanks for your time.

[orizi]

@orizi reviewed all commit messages and made 2 comments.
Reviewable status: 0 of 4 files reviewed, 3 unresolved discussions (waiting on AaronAjose).

---

crates/cairo-lang-parser/src/diagnostic.rs line 235 at r2 (raw file):

                    )
                } else {
                    format!(

i

---

crates/cairo-lang-parser/src/diagnostic.rs line 239 at r2 (raw file):

                         `&&` (for example, `a < b && b < c`)."
                    )
                }

this does not make sense at the general case.
should be only on a a < b < c.

Code quote:

                } else {
                    format!(
                        "{message} If this was intended as a chained comparison, rewrite it with \
                         `&&` (for example, `a < b && b < c`)."
                    )
                }