Overhaul screensavers

[SeanPM5]

Screensavers that would play on living room TV used to use an input_select. I am migrating them to be conditional buttons instead, so I guess they'd be switches. Would have the additional benefit of voice control (ie "Hey Google, turn on living room aquarium screensaver").

Checklist:

• [ ] Break these out into an included file located at /lovelace/cards/screensaver.yaml
• [x] Rename the entity_id from input_select.living_room_screensaver to something more generic, since end goal is to play these on any Cast-enabled device
• [ ] Create a custom logbook entry for which screensaver was activated
• [ ] Keep track of how many times screensaver used with counter component
• [ ] If the Chromecast Harmony activity or TV harmony activity is turned off, reset the input_select to the default value (Select Screensaver) this way the button doesn't remain in on state.

[SeanPM5]

Considering creating a decluttering-card template instead, would make the code a lot cleaner and easier to update. Something along the lines of this.

- type: custom:decluttering-card
  template: screensaver
  variables:
    - name: Aquarium
    - icon: mdi:fish
    - screensaver: https://www.youtube.com/watch?v=XVkADAwOXnU
    - sound: yes

This would make other things more difficult though - voice controls, companion lighting scenes, and most importantly being able to see the state for use in other automations. I want to know whether a screensaver is active or not.