Antibot checkbox is confusing when the module is configured to protect webforms

Problem/Motivation

Antibot third party hooks provide a setting to protect each individual webform, or even one setting to protect them all, in which case, the individual webform setting would be disabled.

However Antibot module provides an easier way to protect all webforms at once, using its UI settings, where you can specify the form IDs that should be protected, using wildcards. So there you can add webform_submission*, and that would protect all webforms.

We ran into confusion when we had that setting in Antibot, and we could still enable or disable the antibot third party checkbox in each webform. We had to do some testing enabling and disabling to figure out what would be the behavior and prevalence, noticing that no matter what we do in the webform configuration, the antibot module setting is already protecting all webforms.

Proposed resolution

To avoid this confusion it would be nicer to improve the antibot's third party UI in the webform configuration, so it webforms are already protected with webform_submission* by antibot module configuration, we would disable the checkbox (with value 1 as protected) in the third party settings of each webform and all webforms settings.