chore: Report which module is at fault, when raising an error about relationship domain inclusion

[sevenseacat]

My app is an Ash 2 app but the error is the same (s/api/domain/)

When an error is raised about resources not being included in the same API, the error didn't actually tell you what module it was coming from:

** (EXIT from #PID<0.98.0>) an exception was raised:
    ** (RuntimeError) Resource `MyApp.Location` in relationship `:location` is not in api `MyApp.Schematics`. Please do one of the following

1. add the resource to the api `MyApp.Schematics`
2. configure a different api

        (ash 2.21.15) lib/ash/api/verifiers/validate_related_resource_inclusion.ex:67: anonymous fn/4 in Ash.Api.Verifiers.ValidateRelatedResourceInclusion.verify/1
        (elixir 1.15.4) lib/enum.ex:1693: Enum."-map/2-lists^map/1-1-"/2
        (ash 2.21.15) lib/ash/api/verifiers/validate_related_resource_inclusion.ex:16: anonymous fn/4 in Ash.Api.Verifiers.ValidateRelatedResourceInclusion.verify/1
        (elixir 1.15.4) lib/enum.ex:2510: Enum."-reduce/3-lists^foldl/2-0-"/3
        (ash 2.21.15) lib/ash/api/verifiers/validate_related_resource_inclusion.ex:15: Ash.Api.Verifiers.ValidateRelatedResourceInclusion.verify/1
        lib/myapp/schematics/schematics.ex:1: anonymous fn/1 in MyApp.Schematics.__verify_spark_dsl__/1
        (elixir 1.15.4) lib/enum.ex:984: Enum."-each/2-lists^foreach/1-0-"/2
        lib/myapp/schematics/schematics.ex:1: MyApp.Schematics.__verify_spark_dsl__/1

By adding the source module name to the error message, now you know where to look!

Contributor checklist

• Bug fixes include regression tests
• Chores
• Documentation changes
• Features include unit/acceptance tests
• Refactoring
• Update dependencies

[zachdaniel]

🚀 Thank you for your contribution! 🚀