Currently, the course tools page loads a reportbuilder report, which uses the data in the lti_types and lti_coursevisible tables to show whether a tool has "Show in activity chooser" set. lti_coursevisible is a course-level override of the lti_types.coursevisible value, and may not exist, but takes precedence if it does exist.

With the introductions of tool placements in MDL-84415, we can now have an lti_placement record associated with each lti_types record (the tool configuration), and additionally, we have a lti_placement_status table which acts like the lti_coursevisible table did; it's a context-level override to the placement status. Each placement has config in lti_placement_config and that config will contain a named config item 'default_usage' which stores either 'enabled' or 'disabled', and indicates the default value of the placement in a context where there does not yet exist a context-level override. It's basically the replacement for lti_types.coursevisible, in the same way that lti_placement_status replaces the lti_coursevisible records. The order of precedence acts the same way.

This issue is scoped with updating the report builder logic + toggle logic to read from and update the placement_status table, instead of the soon-to-be-defunct 'lti_coursevisible' table.
We need to:

1. Make sure the report loads the value of "show in activity chooser" from the lti_placement_config + lti_placement_status tables. Like with coursevisible, it should fall back to the top level config value if the context-level value isn't present.
2. Create a new webservice which toggles the value of a placement_status for a context, and use that in the reportbuilder, when using the toggle.
3. Deprecate the old toggle_showinactivitychooser web service
4. Update behat tests (we need to update the generators first, to make sure that placements + config are being created in the setup steps like 'Given the following "core_ltix > tool types" exist:'
5. We should omit the "Show in activity chooser" toggle from the column if the tool does not support the placementtype (i.e. there is not a record in lti_placement for the given tool and placementtype).

Note: this is an interim fix given we don't yet have a UX mockup of placement management for course tools. However, the web service will be reusable when that time comes.