add a way to inject metadata into oban jobs

[kevinschweikert]

Code of Conduct

• I agree to follow this project's Code of Conduct

AI Policy

• I agree to follow this project's AI Policy, or I agree that AI was not used while creating this issue.

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

I thought read_metadata would allow we to inject metadata into the job like documented in the options for https://oban.hexdocs.pm/Oban.Job.html#new/2
But it just passes the metadata into the trigger action and this would only allow us to manipulate job args which influence uniqueness checks.

Describe the solution you'd like

a way to inject oban metdata options into a job. this also would help job introspection in the oban web dashboard (see screenshot).
Maybe in the same change, rename read_metadata in something else to not confuse the two concepts.

Describe alternatives you've considered

Additional context

[zachdaniel]

I'm open to ideas, but I'd suggest job_metadata is reasonable and the confusion is manageable until a major release.

[sorentwo]

For what it's worth, meta is widely used internally by Oban (especially Pro), and somewhat for internal use. Unless it's for something truly tangential, like an instrumentation span, I'd recommend using args instead.

[zachdaniel]

Makes sense 👍. I don't see a reason for us to necessarily prevent it, but in general yeah everything uses args I don't think anything else currently lets you set actual meta.