Feat: Added <select> to control enabling players on Monitor page

[IgorA100]

The code implements support for disabling ALL players, including "ZMS MJPEG", but the UI does not currently use disabling all players. Because at the moment I am not sure that it is necessary to disable all players.
To implement enabling/disabling "ZMS MJPEG" you need to uncomment some lines of code and add a field to the DB ALTER TABLE MonitorsADD COLUMNZMSEnabledBOOLEAN NOT NULL default true AFTERDecoding``

It looks like this: #4393 (comment)

Also added the ability for <input> to use ".disabled", because if you use the "disabled" attribute for <input>, then the value of <input> will not be used in the form. And now, if you add the "disabled" class, then the value of <input> will be used in the form, but you cannot change its value manually in the UI.

If this PR is approved, then in the future you can remove the checkboxes for controlling player enablement from the UI and visually combine the options into the Go2RTC, RTSP2Web & Janus groups

I'm not sure about the feasibility of this PR, but I had some ideas and decided to publish them. Probably, choosing to enable/disable players in one place (in "multi select") is better than many checkboxes.

[IgorA100]

This PR is not needed?

[IgorA100]

@connortechnology
Haven't you watched this PR yet?
I'm interested in your opinion.

[connortechnology]

It is not clear to me why we would want to disable ZMS playback. The .disabled stuff makes sense.

[IgorA100]

disable ZMS playback

This PR does NOT disable ZMS playback!
The code to disable ZMS playback does exist, but it's locked!

At first, I thought about disabling all players, including ZMS, but I later realized that wasn't necessary and locked the code.

This PR changes the player selection style. I plan to remove the checkboxes (which are quite confusing if there are more than two players) and switch to multi-select. I think it will be more convenient and look better.