refactor: `hamilton.exceptions`

Given the increasing complexity of the library, it could be valuable to create custom exceptions rather than generic `ValueError` and `KeyError`.

This helps with:
- readability: the name of the exception is informative `EdgeTypeMismatchException`, `UnknownNodeException`, `MaterializationError`
- maintainability: the exceptions can be gradually improved by modifying the message in a central place instead of attaching custom messages to individual `KeyError` around the codebase
- debugging: maintainers and users can make a better use of the debugger and exception handling to debug and test their code

related:
- #1218

Start by reading the hamilton.exceptions module and the related discussion in issue #1218, then locate the generic ValueError and KeyError usages across the library. Done should mean the proposed custom exceptions are defined and adopted consistently, with their messages centralized and covered by appropriate tests.

Written by the indexing model from the issue text.