Remove: the webdack gem

[colinbruce]

What

Try removing the webdack gem as it was used 5 years ago to change a table and has only been referenced in migration files, not actively used, since.

• To simulate a normal branch, I had to add an empty commit and allow github to build a standard image and deploy it, before we remove the gem and migrations

Discussion

How do people feel about older migrations being deleted?
The opinion online is that devs should use rails db:schema:load or rails db:prepare instead of rails db:migrate and running everything since day one.

I found one medium article saying they deleted migrations older than 3 months!? 🤔
https://medium.com/clutter-engineering/cleaning-up-old-rails-migrations-1b55b638abb5

Checklist

Before you ask people to review this PR:

• Tests and rubocop should be passing: bundle exec rake
• Github should not be reporting conflicts; you should have recently run git rebase main.
• There should be no unnecessary whitespace changes. These make diffs harder to read and conflicts more likely.
• The PR description should say what you changed and why, with a link to the JIRA story.
• You should have looked at the diff against main and ensured that nothing unexpected is included in your changes.
• You should have checked that the commit messages say why the change was made.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information