FFS-2466: Infer supported jobs from within Pinwheel subclass

[allthesignals]

Ticket

Addresses FFS-2466.

Changes

This makes the model infer the pinwheel accounts supported jobs through the provided pinwheel_account_id.

Context for reviewers

We need to do this to make it easier to support multi-provider. The reason for this is that we want to create a payrol_acount earlier in the process, not when the webhook is received. In order to do that, we needed a tidier way to create payroll account objects.

Before, we would look up the support jobs in the events controller and provide that to the model.

Now, we do that in an after_create hook. This means we can create payroll acounts anywhere without also needing to supply the supported jobs.

Acceptance testing

• No acceptance testing needed
  • This change will not affect the user experience (bugfix, dependency updates, etc.)
• Acceptance testing prior to merge
  • This change can be verified visually via screenshots attached below or by sending a link to a local development environment to the acceptance tester
  • Acceptance testing should be done by design for visual changes, product for behavior/logic changes, or both for changes that impact both.
• Acceptance testing after merge
  • This change is hard to test locally, so we'll test it in the demo environment (deployed automatically after merge.)
  • Make sure to notify the team once this PR is merged so we don't inadvertently deploy the unaccepted change to production. (e.g. :alert: Deploy block! @ffs-eng I just merged PR [#123] and will be doing acceptance testing in demo - please don't deploy until I'm finished!)

[tdooner]

(Hmm thinks to self. Maybe we should save platform_id in the table itself.)

[tdooner]

Would be good to make these methods private

[tdooner]

FWIW, I don't love making API calls to 3rd party services on model creation. Probably not the best practice because it might make testing harder. But it seems ok for now, and we can refactor it later if it becomes annoying.