Adds migration for search triggers

[mouse-reeve]

Description

It looks like there are migrations that need to happen for the search vector triggers, but I'm not sure why? This seems to be the most recent commit to modify the search vectors and it contains migrations: 0795b4d

@BartSchuurmans @dato might have an insight here?

• Related Issue #
• Closes #

What type of Pull Request is this?

• Bug Fix
• Enhancement
• Plumbing / Internals / Dependencies
• Refactor

Does this PR change settings or dependencies, or break something?

• This PR changes or adds default settings, configuration, or .env values
• This PR changes or adds dependencies
• This PR introduces other breaking changes

Details of breaking or configuration changes (if any of above checked)

Documentation

• New or amended documentation will be required if this PR is merged
• I have created a matching pull request in the Documentation repository
• I intend to create a matching pull request in the Documentation repository after this PR is merged

Tests

• My changes do not need new tests
• All tests I have added are passing
• I have written tests but need help to make them pass
• I have not written tests and need help to write them

[dato]

I think this might go away if you update sqlparse in your virtualenv? (See #3400)

[mouse-reeve]

That did it, thank you! I thought there was probably something obvious I was missing.