[CHORE] Remove support for row-level "disabled" property in favour of component param

[jfmcquade]

What?
Following on from #2757, it was agreed that the row-level "disabled" property, which is not currently used, should be deprecated in favour of a component-level disabled param.

Why?
Having a row-level property (represented by a column in a template sheet) implies that the property has a meaning for all (or many) row types. For a property like disabled, which must be handled by components on a case-by-case basis, this property belongs in the parameter list. Additionally, having a disabled column alongside condition and hidden is confusing.

How?
See list of components that currently consume the row.disabled property. These should be refactored to expose a disabled parameter:

The only example of an authored row.disabled property within the debug deployment sheets is in example_workshops_accordion.