Support user-provided JQ modules

Is your feature request related to a problem? Please describe.

I frequently have to replicate filters between numerous Weaver configurations in order to support providing our customers with a consistent SDK across languages. It would be great to consolidate the filtering logic alongside my registry definitions and templates.

Describe the solution you'd like

Forge currently loads a default module while provides the helper functions authors would typically use for their template generation. It would be great if we could supply additional modules to load via the weaver generate command.

Describe alternatives you've considered

Many warts encountered when dealing with deprecated elements could be worked around by adding a exclude_attribute and exclude_metric option on the relevant functions, however, user-defined JQ modules would provide better composition long-term under the multi-registry support model.

Start with the weaver generate command and the default module at defaults/jq/semconv.jq; trace how that module is loaded during template generation. Review the multi-registry context described in the issue and determine the supported way to provide additional user modules. Done means user-provided JQ modules can be loaded alongside the default helpers for generation.