fix(compiler): Throw an error when comparing an alias and a named type with the same name [LNG-231]

[DieMyst]

Description

Throw compilation error on a code like this:

alias NamedT: u32

func test():
  MyAbility = NamedT(randomField = "sf")

Implementation Details

Don't ignore named type comparison with aliases, improve type checking error.

Checklist

• Corresponding issue has been created and linked in PR title.
• Proposed changes are covered by tests.
• Documentation has been updated to reflect the changes (if applicable).
• I have self-reviewed my code and ensured its quality.
• I have added/updated necessary comments to aid understanding.

Reviewer Checklist

• Tests have been reviewed and are sufficient to validate the changes.
• Documentation has been reviewed and is up to date.
• Any questions or concerns have been addressed.

[linear]

LNG-231 Fix NamedType creation with improper types

aqua:

alias Troll: string

func test() -> i8:
  MyAbility = Troll(lololo = 1, trololo = 2)

  <- 42

compiles and produces air, but should not

also it seems to crash aqua vscode extension

[InversionSpaces]

Suggested change

	val expectedStr = alias.map(a => s"$a, that is an alias of '$expected'").getOrElse(expected.toString)
	val expectedStr = alias.map(a => s"$a (an alias of '$expected')").getOrElse(expected.toString)

[InversionSpaces]

I don't like adding this argument here. TypesAlgebra is the one that should know about type aliases, it should not get this info from outside, should it?
Maybe lets add a separate method resolveNamedTypeConstruction, which will take named type token and field types, then resolve the type and report a error if the type is not data or ability?

[InversionSpaces]

Remove println in tests from previous PR here, please

[InversionSpaces]

nit: I believe we should move towards OptionT because we have F[Option[A]] almost all the time and it produces a lot of such flatMap(_.flatTraverse( chains. But I am not insisting on rewriting this right now

[InversionSpaces]

I believe result type is better to be NamedType instead of Type, or even AbilityType | StructType, to avoid pattern matching on call site