Added isKey and getType methods to Preferences documentation

[Viproz]

Description of Change

Addition of documentation for the functions isKey and getType for the Preferences libraries.
These functions were added here #4441 but not documented.

Tests scenarios

I have not tested, no code change only a change in the rst file

Related links

Documents PR #4441
Adds documentation for issue #4440

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Warnings

⚠️

Some issues found for the commit messages in this PR: the commit message "Added isKey and getType methods to the documentation": summary looks empty type/action looks empty Please fix these commit messages - here are some basic tips: follow Conventional Commits style correct format of commit message should be: <type/action>(<scope/component>): <summary>, for example fix(esp32): Fixed startup timeout issue allowed types are: change,ci,docs,feat,fix,refactor,remove,revert,test sufficiently descriptive message summary should be between 20 to 72 characters and start with upper case letter avoid Jira references in commit messages (unavailable/irrelevant for our customers) TIP: Install pre-commit hooks and run this check when committing (uses the Conventional Precommit Linter).

👋 Hello Viproz, we appreciate your contribution to this project!

---

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 6635b46

[me-no-dev]

Thanks @Viproz !

[Xylopyrographer]

When the Preferences API and Tutorial docs were released under #6442, it included details on getType, which can be seen here as well: https://espressif-docs.readthedocs-hosted.com/projects/arduino-esp32/en/latest/api/preferences.html

So I understand, wondering how getType went missing in the doc?

[Viproz]

My bad sorry, getType is written twice in my version, only isKey needed to be added, do you want me to submit a new PR with the second getType removed?

[Xylopyrographer]

@Viproz That would be great. 👍

Would you also be able to submit a new PR with that correction to the release/v2.x branch so it gets back ported to the pending 2.0.15 release?

Not sure how isKey got missed in the API doc as a use case is presented in the Preferences tutorial. Nice catch 😄.