feat: add Github custom properties table to cloudquery

[tjsilver]

What does this change?

• upgrades github cloudquery plugin to v11 which provides a custom properties table
• creates a github_repository_custom_properties table in prisma schema
• creates the sql migration
• adds the table to the docker-compose so that it can be queried in DEV

Why?

This follows from #1316. Using custom properties will allow us to move away from topics. Custom properties can be
made compulsory, which means we can enforce repos to choose a property.

The production custom property also applies branch protection.

How has it been verified?

• Migration applied to CODE - the Github tables are copied from CODE to DEV for local testing
• Tested locally - 14 rows returned

[github-actions]

Deploy build 6213 of deploy::service-catalogue to CODE

All deployment options

• Deploy build 6213 of deploy::service-catalogue to CODE
• Deploy parts of build 6213 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.

[kelvin-chappell]

What does this do?

[tjsilver]

Good question! This means that it's ignored by the Prisma client (see docs). I added @@ignore to this model, as we currently don't need it because we're not doing anything with the table in service catalogue. The model being the schema means that the table will be kept up to date nonentheless, IIUC. When we start to interact with the data via the Prisma client in future work, then we will stop ignoring it.

[kelvin-chappell]

Ah I see. Thanks for the extra info!

[kelvin-chappell]

👍

[akash1810]

Should we explicitly add this new table to the ones we're collecting?