[Docs]: Update Usage Example for block variation picker: Fix Import from Wrong Package

[jawadmalikdev]

What?

I updated the documentation for using the block variation picker component with the correct code.
Initially, the store was imported from the wrong package, which was @wordpress/block-editor, and it was imported as "blockEditorStore" However, in the code, it's referred to as "blocksStore"

Why?

The usage example can be confusing for users and might make it difficult for them to troubleshoot the issue. However, the problem is simply due to importing from the wrong package.

How?

I fixed the import to use the right package, which is @wordpress/blocks. I also imported the store as "blocksStore" and that's what being used in the code.

[github-actions]

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @jawadhere! In case you missed it, we'd love to have you join us in our Slack community, where we hold regularly weekly meetings open to anyone to coordinate with each other.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

[ajitbohra]

👍 LGTM

[Mamaduka]

Hi, @jawadmalikdev

Do you mind rebasing this branch on top of the latest trunk? That should fix the CI checks.

Thanks!

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @jawadmalikdev.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Unlinked contributors: jawadmalikdev.

Co-authored-by: ajitbohra <[email protected]>
Co-authored-by: Mamaduka <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[jawadmalikdev]

@Mamaduka I have rebased it on the latest trunk.

Plz have a look.

Thanks!

[github-actions]

Congratulations on your first merged pull request, @jawadmalikdev! We'd like to credit you for your contribution in the post announcing the next WordPress release, but we can't find a WordPress.org profile associated with your GitHub account. When you have a moment, visit the following URL and click "link your GitHub account" under "GitHub Username" to link your accounts:

https://profiles.wordpress.org/me/profile/edit/

And if you don't have a WordPress.org account, you can create one on this page:

https://login.wordpress.org/register

Kudos!