Add LFK ci_pipeline_artifacts to projects on project_id

What does this MR do and why?

Per &7249 (closed)

As part of our CI "decomposition" efforts we need to remove all foreign keys that are cross-database (ie. between the planned main and ci databases). We are going to replace them all with "loose foreign keys".

These loose foreign keys are the first step to removing the cross-database foreign keys between main and ci databases.

Related issue: #348267 (closed)

Validations

• Best team to review (check off when reviewed): grouptesting devopsverify
• No way for user to access once parent is deleted. Please explain:
• Possible to access once parent deleted but low user impact. Please explain: @morefice

  This is being for users with codequality enabled and code coverage. I think this is fine as if the project gets deleted users should not be able to access merge requests.

• Possible Sidekiq workers that may load directly and possibly lead to exceptions. Please explain:
• Possible user impact to be evaluated or mitigated. Please explain:

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.