Add scan interval to Command Line

[gjohansson-ST]

Proposed change

Add scan interval option to Command Line (lost when moving to integration key YAML)

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)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes command_line sensor SCAN_INTERVAL support #93949
• This PR is related to issue:
• Link to documentation pull request: Add scan_interval option to Command line home-assistant.io#27580

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
• I have followed the perfect PR recommendations
• 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.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[parautenbach]

I thought there was a move away from any sensor having a configurable scan interval. I understood the directive to be:

• There's a default built-in of 30 sec.
• Via the UI you can only turn it on or off.
• If off, you customise it using an automation.

I mean, I don't really care. I just remember massive debates when the team started to remove this, so it's strange to see a change where it's added again for an integration.

[gjohansson-ST]

• Via the UI you can only turn it on or off.

It's not UI based

[balloob]

@parautenbach you are correct for UI-based integrations. Command-line is not UI-based as it allows arbitrary command execution.