Ignoring expression and type columns from compliance requirement

What does this MR do and why?

With introduction of new table compliance_requirements_controls for storing the controls for a requirement, we don't need the control_expression and requirement_type columns anymore. So as per https://docs.gitlab.com/ee/development/database/avoiding_downtime_in_migrations.html, ignoring the columns in this MR and removing all usages of the columns in the code. Please note that the graphql apis are in experiment so we can directly remove the attributes from them and these columns are pretty new and the feature is not released yet, so it is safe to remove them.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

How to set up and validate locally

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

Related to #513467 (closed)