Remove old Automate Transfer AP scope from timers scope dependencies

[MaxTueckeGlobus]

sc-35400

Bugfixes

• Removed the old Automate Transfer AP scope from timers scope dependencies.
• Updated CURRENT_SCOPE_CONTRACT_VERSION and timers min_contract_version from 1 to 2.

Testing

• Updated existing tests with the new scope dependencies.
• Manual testing done:
  • With the existing timers tokens present, was able to create a new timer w/ data_access
  • With the existing timers tokens present, was able to create a new timer w/ no data_access
  • With no tokens present, was able to create a new timer w/ data_access
  • With the new timers tokens present, was able to revert and create a new timer w/ data_access (simulating a CLI downgrade)

[ada-globus]

Did you find that this was behaviorally beneficial? I'm wondering if/how it helps, given that the current scope requirements are a subset of the prior ones (to be clear: this is not a leading question, it's a genuine inquiry on what you found).

[MaxTueckeGlobus]

The version bump wasn't outright required for the changes to function correctly, but I decided to go with it since I felt the spirit of the story was making sure we had the “correct” solution. So even though the users' old tokens would work, they should still be forced to make the new “correct” ones.