feat: add vault and consul token to job resource

[anth0d]

There is an implicit cyclic dependency between providers when you try to use dynamic (i.e., generated by another provider) vault_token and consul_token in your Nomad provider configuration. This change introduces the ability to provide vault_token and consul_token as part of the nomad_job resource, so that dynamic token values can be provided by vault and consul providers respectively without hitting the provider dependency issue.

Let me know how I can ensure the registry docs are also up to date with this change, and let me know if anything else is needed! Thanks!

[lgfa29]

Thanks @anth0d, and sorry for the delay in getting this reviewed.

I pushed a commit adding a note to the docs about storing these sensitive values in the state.