Add tests for recursive const definitions and associated consts usages

[ironcev]

Description

This PR adds additional tests for constants. Those test cases are important for the implementation of #6351 which will completely restructure compilation of constants.

Tests for recursive const definitions should also be considered before we start implementing const fn and const trait. In particular, we want to better track and provide precise error messages in case of unintended attempt to recursively define a constant in a complex situation that includes const fn and const trait.

Related to #6534, #6537, #6538, #6539, #6540, #6543, and #6544.

Checklist

• I have linked to any relevant issues.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation where relevant (API docs, the reference, and the Sway book).
  • If my change requires substantial documentation changes, I have requested support from the DevRel team
• I have added tests that prove my fix is effective or that my feature works.
• I have added (or requested a maintainer to add) the necessary Breaking* or New Feature labels where relevant.
• I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
• I have requested a review from the relevant team or maintainers.

[sdankel]

lgtm!