Register builtins during scoping and report proper errors instead of crashing

[janmasrovira]

This pr has two relevant changes:

Errors instead of crases

When registering a builtin, we perform some sanity checks. When unsuccessful, the compiler crashes. This seldom happens because builtins are defined in libraries that we write ourselves. However, any compiler crash is a bug, so this pr refactors these crashes into proper errors.

Registering builtins during scoping

Before this pr, builtins are registered and sanity checked during the translation from Concrete to Internal. This imposes that the order in which we translate stuff is relevant, as we must register a builtin before we use it. For the most part this is fine when the dependency is explicit in the code, but sometimes there are explicit dependencies. E.g. do notation and the builtin monad-bind. In order to avoid adding special rules, it is easier to just register builtins during scoping, so I've refactored the code to do this.

I've also removed the Builtins effect and moved its methods to the InfoTableBuilder since the builtins table is now part of the Scoped InfoTable. Consequently, I've removed the the field _artifactBuiltins.

Future work

• Fix It is possible to define the same builtin twice without an error #2952. I didn't find a good way to fix this problem in this pr, so it is left for a separate pr.