Add 'migrate_projects' column to bulk_import_entities table

What does this MR do and why?

This MR adds migrate_projects column to bulk_import_entities table. It's going to be used to allow granularity in imports, to indicate whether a user wants to migrate projects with their groups.

Mentions #383332 (closed)

db:check-migrations

Migration output

$ scripts/validate_migration_schema
$ git diff --name-only --diff-filter=A master -- db/migrate db/post_migrate
db/migrate/20230111092510_add_migrate_projects_to_bulk_import_entities.rb
$ scripts/db_tasks db:migrate:down VERSION=20230111092510
main: == 20230111092510 AddMigrateProjectsToBulkImportEntities: reverting ===========
main: -- remove_column(:bulk_import_entities, :migrate_projects, :boolean, {:null=>false, :default=>true})
main:    -> 0.0133s
main: == 20230111092510 AddMigrateProjectsToBulkImportEntities: reverted (0.0218s) ==
$ scripts/db_tasks db:schema:dump
$ git diff master -- db/structure.sql
$ scripts/db_tasks db:migrate
main: == 20230111092510 AddMigrateProjectsToBulkImportEntities: migrating ===========
main: -- add_column(:bulk_import_entities, :migrate_projects, :boolean, {:null=>false, :default=>true})
main:    -> 0.0067s
main: == 20230111092510 AddMigrateProjectsToBulkImportEntities: migrated (0.0117s) ==

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.