[JENKINS-60866] Remove attributes from f:toggleSwitch

[daniel-beck]

See JENKINS-60866.

A quick GH search indicates that nobody uses this element yet (it was introduced only in #5923, apparently as an indiscriminate copy & paste from existing controls), so now's a good time to remove attributes that will be annoying to support. #6852 deprecates the same attributes in f:checkbox.

Proposed changelog entries

• Remove onclick and disabled attributes from f:toggleSwitch.

Proposed upgrade guidelines

N/A

Submitter checklist

• (If applicable) Jira issue is well described
• Changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developer, depending on the change) and are in the imperative mood. Examples
  • Fill-in the Proposed changelog entries section only if there are breaking changes or other changes which may require extra steps from users during the upgrade
• Appropriate autotests or explanation to why this change has no tests
• New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadoc, as appropriate.
• New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO") if applicable.
• For dependency updates: links to external changelogs and, if possible, full diffs

Desired reviewers

@mention

Maintainer checklist

Before the changes are marked as ready-for-merge:

• There are at least 2 approvals for the pull request and no outstanding requests for change
• Conversations in the pull request are over OR it is explicit that a reviewer does not block the change
• Changelog entries in the PR title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood
• Proper changelog labels are set so that the changelog can be generated automatically
• If the change needs additional upgrade steps from users, upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the PR title. (example)
• If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[jasoncwa]

These features were in use in a non-public facing plugin I maintain. Is there an alternative way to trigger events onclick without these attributes?

[timja]

Yes use JavaScript and register an event listener using an id or class to lookup the component

[daniel-beck]

… as is documented in the other, similar control, whose corresponding PR #6852 is linked in the original PR comment.