Add new component renault documentation

[epenet]

Proposed change

Type of change

• Spelling, grammar or other readability improvements (current branch).
• Adjusted missing or incorrect information in the current documentation (current branch).
• Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • I've opened up a PR to add logo's and icons in Brands repository.
• Added documentation for a new feature I'm adding to Home Assistant (next branch).
• Removed stale or deprecated documentation.

Additional information

• Link to parent pull request in the codebase: Add renault integration core#39605
• Link to parent pull request in the Brands repository: Add new component renault logo and icon brands#1825
• This PR fixes or closes issue:

Checklist

• This PR uses the correct branch, based on one of the following:
  • I made a change to the existing documentation and used the current branch.
  • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
• The documentation follows the Home Assistant documentation standards.

[epenet]

@frenck you asked on the main PR that I remove the extra platforms (binary_sensor, climate, device tracker) for the new integration, and follow up with subsequent PRs.
For the documentation is it best to keep in sync with the main PR, or set the documentation PR as we hope it will be when all the subsequent PRs are merged?

[frenck]

The documentation must match the linked PR

[frenck]

✅ Approved. Can be merged as soon as the parent PR gets merged.

[epenet]

Hi @frenck,

Following the discussions on the main PR, I have amended the documentation with a link to the instructions on how to grab the API keys from the Renault servers.

[milanmeu]

@frenck Parent merged.
This should be merged to the current branch because the integration is already available in 2021.8.

The base branch was changed.

[probot-home-assistant]

It seems that this PR is targeted against an incorrect branch since it has a parent PR on one of our codebases. Documentation that needs to be updated for an upcoming release should target the next branch. Please change the target branch of this PR to next and rebase if needed.
_{^{(message by DocsTargetBranch)}}