Add initial rest query params

[boxcee]

Breaking change

Proposed change

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:

sensor:
- platform: rest
  resource_template: 'https://revgeocode.search.hereapi.com/v1/revgeocode'
  params:
    at: '52.521,13.3807'
    lang: 'en-GB'
    apiKey: !secret apiKey
  value_template: '{{ value_json["items"][0]["address"]["district"] }}'

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request: Add rest query params documentation home-assistant.io#15352

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 @fabaff, mind taking a look at this pull request as its been labeled with an integration (scrape) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[probot-home-assistant]

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

[fabaff]

Should be parameters.

Suggested change

	CONF_PARAMS = "params"
	CONF_PARAMETERS = "parameters"

[boxcee]

Naming is directly taken from httpx. requests uses the same naming.

[boxcee]

@fabaff

[boxcee]

@bdraco Added the link to the documentation PR in the description.

[bdraco]

LGTM.

I'm going to defer merging in case fabaff feels strongly about the naming.

[boxcee]

Hey @fabaff, can you double-check?

[boxcee]

requests docs: https://requests.readthedocs.io/en/latest/api/#requests.Request
httpx docs: https://www.python-httpx.org/api/#client
treq docs: https://treq.readthedocs.io/en/release-20.9.0/api.html

The three above all use params.

Really looking forward to this feature. Right now I cannot use secrets in query parameters.

Please, take decision: @bdraco, @MartinHjelmare, @fabaff.

[bdraco]

Please do not ping reviewers. There is a significant backlog of PRs to review, and working though additional notifications only slows things down.