Disable instance-wide uncommitted queue warning for production class

[isc-pbarton]

This came up as a concern with a HealthConnect Cloud customer. Many people are editing the production class in different namespaces. Each time you go to edit the production class, you'll get a warning that somebody else is also editing it. Making a change to the production will make the warning go away, but it will come back if you commit the change.

Just for the production class, the warning can be noisy and unhelpful especially since most merge conflicts will be automatically resolved anyway.

[isc-bspead]

Pravin - with Production Decomposition coming, is it worth excluding the Production from the warning? I am wondering if we want to maintain visibility about the potential for merge conflicts for those sites that decide to not use Production Decomposition. Those using Decomposition will no longer see this unless they are editing the same PTD (in which case we definitely want the warning).