Add GoodJob as Active Job backend

[ellery-nava]

Ticket

• Resolves Recommend default queuing backend for Active Job #25

Changes

• Add GoodJob gem and migration to install
• Update notification service to deliver later

Context for reviewers

Background context, more in-depth details of the implementation, and anything else you'd like to call out or ask reviewers.

Testing

• Changes tested as part of the pfml-starter-kit-app repo

[rocketnova]

Generally looks great. Could you add an ADR for this into /docs/app-rails/decisions? Thank you!

[rocketnova]

Do you think we need a queue_name_prefix?

[ellery-nava]

You have a lot more Rails expertise than I do so please LMK if this is the wrong line of thinking, but since jobs are queued using a table in the DB I don't think that we'd need to worry about a prefix since we won't be sharing the database across environments? I would think that the queue prefix might be more necessary if we were doing something like sharing a Redis instance across multiple environments, for example.

[rocketnova]

since jobs are queued using a table in the DB I don't think that we'd need to worry about a prefix since we won't be sharing the database across environments?

Good point!

[rocketnova]

After looking at this and thinking about it more, I think we should move this line:

  config.active_job.queue_adapter = :good_job

out of the per-environment files and into /app-rails/config/application.rb. What do you think? Good Jobs should definitely be used in the mock-production environment. I'm not sure what it might do to the test environment, though. Thoughts?

[rocketnova]

This should get moved to an ADR and a link to that should be added here.

[ellery-nava]

Will do, thanks!