Support disabling of bound tools

See discussion in lhcb/Rec!2660 (comment 5106524)

Follows up on !1270 (merged)

mentioned in merge request lhcb/Rec!2660 (merged)

mentioned in merge request lhcb/Moore!1242 (merged)

mentioned in merge request lhcb/Rec!2852 (merged)

One possible solution to this problem would be to only allow support disabling of a 'bound tool' instance if the 'bound tool interface' provides a default do-nothing implementation which can be passed to the user code in case the tool is disabled, i.e. instead of asking the tool implementation to create the 'bound' version, which cannot work as the tool implementation is not there because it has been disabled, create a default do-nothing bound 'box' instead.

mentioned in merge request !1330 (merged)