LF-3651 Revenue type table unique violation error on auto-incrementing primary key

[kathyavini]

Description

This fixes the database error seen on first insert(s) into the new revenue_type table due to the auto-incrementing primary key which was ignored in favour of setting the key explicitly in the migration.

This PR amends the migration file. Affected databases (beta, developer local environments) should be rolled back to before when this migration was run (likely 1 or two 2 batches -- please see your own database's knex_migrations table) and then run again once this PR is merged. You will lose your existing custom revenue types (on beta none exist yet as the API to create them has not been merged).

Jira link: https://lite-farm.atlassian.net/browse/LF-3651

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• Passes test case
• UI components visually reviewed on desktop view
• UI components visually reviewed on mobile view
• Other (please explain)

Was written and tested on local database with all authors @Duncan-Brain and @SayakaOno and @kathyavini

Checklist:

• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• The precommit and linting ran successfully
• I have added or updated language tags for text that's part of the UI
• I have added "MISSING" for all new language tags to languages I don't speak
• I have added the GNU General Public License to all new files

[SayakaOno]

It worked for me!