feat: type path for any type

[asterite]

Description

Problem

Resolves #7767

Summary

In addition to implementing the feature I tried to improve some parser errors. For example if you write:

fn main() {
  let _ = ()::foo();
}

you get this error (in addition to the one about not finding foo):

error: Missing angle brackets surrounding type in associated item path
  ┌─ src/main.nr:2:11
  │
2 │   let _ = ()::foo();
  │           -- Types that don't start with an identifier need to be surrounded with angle brackets: `<`, `>`

That's actually how I learned in Rust that you need to surround types with <..>.

For other types there's a bit of error recovery and cleanup too to make it clear that <...> is missing.For example for:

fn main() {
    (Field, i32)::foo()
}

we get:

error: Missing angle brackets surrounding type in associated item path
  ┌─ src/main.nr:2:5
  │
2 │     (Field, i32)::foo()
  │     ------------ Types that don't start with an identifier need to be surrounded with angle brackets: `<`, `>`

For this:

fn main() {
    [Field; 3]::foo()
}

we get this error:

error: Missing angle brackets surrounding type in associated item path
  ┌─ src/main.nr:2:5
  │
2 │     [Field; 3]::foo()
  │     ---------- Types that don't start with an identifier need to be surrounded with angle brackets: `<`, `>`

Another improvement is that previously Field (in an expression context, without :: following it) would be parsed as a TypePath whose ident is empty (like Field::) which would then lead to a strange error saying that the method '' didn't exist for Field. Here I changed it so that it's parsed as an error, and the error says "Expected value, found built-in type Field" (like in Rust).

Additional Context

We could document this though I don't know where (I couldn't find docs for this for Rust because I don't know what it's called)

Documentation

Check one:

• No documentation needed.
• Documentation included in this PR.
• [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist

• I have tested the changes locally.
• I have formatted the changes with Prettier and/or cargo fmt on default settings.

[github-actions]

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark 'Test Suite Duration'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.

Benchmark suite	Current: 385790c	Previous: 425e102	Ratio
noir-lang_sha512_	30 s	24 s	1.25
olehmisar_noir_webauthn_	2 s	1 s	2
zkemail_zkemail.nr_lib	2 s	1 s	2

This comment was automatically generated by workflow using github-action-benchmark.

CC: @TomAFrench