New implementation of resolving types in get-scope

Motivation and Context

This MR refactors the part in get-scope related to resolving types, This is done in a new module Resolve_types,

Which run the typer for each declaration (does in a manner in which it does it fail, i.e. it tries to type as much of the program as possible (your can think of it was typer that does not fail on error, but accumulates the errors & warnings)

And this module also deals with annotated binders.

Component

• compiler
• website
• webide
• vscode-plugin
• debugger

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Performance improvement (non-breaking change that improves performance)
• None (change with no changelog)

Changelog

Checklist:

• Changes follow the existing coding style (use dune @fmt to check).
• Tests for the changes have been added (for bug fixes / feature).
• Documentation has been updated.
• Changelog description has been added (if appropriate).
• Start titles under ## Changelog section with #### (if appropriate).
• There is no image or uploaded file in changelog
• Examples in changed behaviour have been added to the changelog (for breaking change / feature).