Do not generate DB docs file for p_ci_builds

What does this MR do and why?

Because !115485 (merged) had to be no-oped in !120157 (merged) the table exists in environments that executed the migration. Dropping the table is not really a good option, so we need to temporary ignore this file until the migration is completed on the CI database(gitlab-com/gl-infra/production#14072 (closed)).

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.

Related to #382033 (closed)