Add console preferences migration

[nicholaspcr]

Summary

References #6483

The deadline for the v3.29 is tomorrow and there is still ongoing work for API implementation, making it not viable for being merged and release on this exact version.

Doing just the migrations allows for the development and release of the console_preferences in the v3.29.1, since it won't break the API and the DB changes would still happen on this release.

Changes

• Add necessary migration

Testing

Ran it locally and performed a few user operations.

Regressions

The default value for the new column in the users table is NULL and it should not impact any of the current operations.

Notes for Reviewers

I'm aware that in the enterprise the migration will be a bit different and I'll create a PR for that if this idea is deemed appropriate.

CC @adriansmares @KrishnaIyer

Checklist

• Scope: The referenced issue is addressed, there are no unrelated changes.
• Compatibility: The changes are backwards compatible with existing API, storage, configuration and CLI, according to the compatibility commitments in README.md for the chosen target branch.
• Documentation: Relevant documentation is added or updated.
• The steps/process to test this feature are clearly explained including testing for regressions.
• Changelog: Significant features, behavior changes, deprecations and fixes are added to CHANGELOG.md.
• Commits: Commit messages follow guidelines in CONTRIBUTING.md, there are no fixup commits left.

[adriansmares]

Per compatibility commitment, a v3.29.1 Console must work with an v3.29.0 Identity Server. Even if we migrate the Identity Server in time, the API gap would still be there.

I wouldn't rush this functionality, and instead would prefer that we consider doing this in the next minor. cc @KrishnaIyer for the next stack meeting.

[KrishnaIyer]

ACK. Let's then target this for v3.30.0. We'll create a new target branch and an RFC for that.