Remove DeploymentConfig, Build and BuildConfig sections from navigation and use flags so they can be enabled by cluster admins

There is a workloads change, which is introducing DeploymentConfigs and Builds API as a capabilities, which gives the cluster admin option to enable/disable each of their API.

In case the DeploymentConfigs capability is disabled we should remove the `Deployment Config` subsection from `Workloads` nav section.

In case the Builds capability is disabled we should remove the `Builds` and `Build Configs` subsection from `Workloads` nav section.

• Use console extensions to check for if  DeploymentConfigs, Builds and BuildConfigs are available on the cluster and set appropriate flags which will serve as requirement for console.navigation/resource-ns and console.action/resource-provider