Give correct suggestion for a typo in raw pointers

[Kivooeo]

This adds a check for when user wrote const* T instead of *const T, I just saw how a C-person made this typo and compiler suggests this

 --> src/main.rs:2:17
  |
2 |     let p: const* u8 = 0 as _;
  |                 ^
  |
help: add `mut` or `const` here
  |
2 |     let p: const*mut  u8 = 0 as _;
  |                  +++
2 |     let p: const*const  u8 = 0 as _;
  |                  +++++

which is very incorrect

also fixes #136602

r? compiler

[compiler-errors]

This probably should also be moved into a separate function and also moved way down into the actually if else chain below rather than being hit first on every call to parse_ty_common

[Kivooeo]

This was made exactly like attribute parsing in types right below, this why I originally chose this place and this strategy

About snapshoting I'm not fully sure I can and should use it here, not only because I fully know how and why it should be used, I checked other places where snapshotting was used and it mostly like in Err branch of match which I don't use

About eating Star it looks correct for me here even if we know that here is Star 100% beacuse we checked it in if, but if there any other way more better way to do I'm in full ears, but honestly I dont personally like this if branch here because of unreachable!, so yeah, should be a better way to do it,

I also adressed a wording problem, new one should be more straighforward and clear for end user

And I made a recovery as a TyKind::Ptr, agree that this is better generally

Also about lookahead(2) or can_begin_type I'm not quite sure why we need it, I'm parsing type in if with parse_ty_no_question_mark_recover to create a TyKind::Ptr from it, and if there will be no type at all it should fail earlier with a different error

[Kivooeo]

@rustbot ready