Fix bitbucket folder sync pull

[akshay-gupta7]

Why does this PR exist?

Resolves #3070

In the 2.0 version of the plugin, the users are unable to fetch sets from Bitbucket remote storage, when the sets are in a folder structure. For example if a set exists as folder1/set1, it shall be unable to fetch it and even delete the existing folder sets.

What does this pull request do?

• This PR scans through the response of the Bitbucket API and filters the directories as well(which was earlier being ignored), and then fetches the sets in json format from each of those folders.
• It then scans through all the json files(which was being done previously as well, but now includes the folder structure sets as well)

Testing this change

• Create a set in a folder,
• Add some tokens in the set
• Push to Bitbucket
• Then pull from Bitbucket
• Expected: It should not wipe the folder sets and pull the sets in the folder

[changeset-bot]

🦋 Changeset detected

Latest commit: 92786ad

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@tokens-studio/figma-plugin	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

⤵️ 📦 ✨ The artifact was successfully created! Want to test it? Download it here 👀 🎁

[github-actions]

Commit SHA:576fb0487442f42e97665e696d357a3bd3b96dde

Test coverage results 🧪

Code coverage diff between base branch:main and head branch: fix-bitbucket-folder-sync-pull 

Status	File	% Stmts	% Branch	% Funcs	% Lines
🔴	total	67.94 (-0.02)	58.69 (-0.01)	64.72 (-0.03)	68.33 (-0.02)
🔴	packages/tokens-studio-for-figma/src/storage/BitbucketTokenStorage.ts	63.63 (-3.03)	63.41 (-0.69)	68.42 (-6.58)	63.51 (-3.15)

[github-actions]

Commit SHA:576fb0487442f42e97665e696d357a3bd3b96dde
Current PR reduces the test coverage percentage by 1 for some tests

[six7]

super minor comments, otherwise good to merge!