Add not null constraint on project_id/group_id/organization_id to jira_tracker_data table

Once all existing records are backfilled and there are no records without sharding key we can create a post deployment migration to set a multicolumn not null constraint on project_id/group_id/organization_id for the jira_tracker_data table.

Make sure to finalize the batched background migration before setting not null constraint #524679 (closed)