Add mode info attributes to script and automation

[bramkragten]

Proposed change

Adds attributes to scripts and automations about the current mode/max/number of running.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

[probot-home-assistant]

Hey there @home-assistant/core, mind taking a look at this pull request as its been labeled with an integration (script) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[balloob]

FYI @pnbruckner

[balloob]

This is going to be a breaking change for Homekit I think? (breaking has already happened in the other PR)

I wonder if Homekit should just always make these "activate only"?

CC @bdraco

[bramkragten]

It shouldn't be breaking I guess, can_cancel would always be true.

[bdraco]

In frontend we probably should adjust this?

src/panels/lovelace/entity-rows/hui-script-entity-row.ts:        ${stateObj.attributes.can_cancel
src/state-summary/state-card-script.js:        <template is="dom-if" if="[[stateObj.attributes.can_cancel]]">
src/state-summary/state-card-script.js:        <template is="dom-if" if="[[!stateObj.attributes.can_cancel]]">

EDIT: home-assistant/frontend#6371

[bramkragten]

In frontend we probably should adjust this?

src/panels/lovelace/entity-rows/hui-script-entity-row.ts:        ${stateObj.attributes.can_cancel
src/state-summary/state-card-script.js:        <template is="dom-if" if="[[stateObj.attributes.can_cancel]]">
src/state-summary/state-card-script.js:        <template is="dom-if" if="[[!stateObj.attributes.can_cancel]]">

home-assistant/frontend#6371