Convert errors into Actions-compatible logging with annotations

[JamesMGreene]

• Towards Supported configuration file extension check does not use the per-generator default #104

... As a result, if generator_config_file is not specified, then errors within the setPagesConfig function will always be blamed on an incorrect file extension.

The behavior describes in that blurb is mostly due to the fact that we were incorrectly passing the Error object as the second parameter to core.error/core.warning/core.notice when those methods are actually expecting an AnnotationProperties object with error-like metadata.

This PR updates the messages being logged to include the error.message, as well as including the error stack frame information in the AnnotationProperties optional arugment.