[Bug]: Fix the collection installation on github and user space

[Driss-Lalami99]

Description

when you install a collection from the prompt registry marketplace, there are three options and they all represent bugs:
option 1: installation in .github/ folder with no exclude option.
Bug: when you install with .github/ folder option the collection is installed directly under \AppData\Roaming\Code\User\globalStorage\amadeusitgroup.prompt-registry\bundles\coaching-prompt instead of installing the collection in repo level, this is critical especially for skills who do not unless they are under .github/ folder in the repo level and still needs to be fixed for all the other primitives

option 2: installation in .github/ folder with exclude option.
Bug: when you install with .github/ folder option the collection is installed directly under \AppData\Roaming\Code\User\globalStorage\amadeusitgroup.prompt-registry\bundles\coaching-prompt instead of installing the collection in repo level, this is critical especially for skills who do not unless they are under .github/ folder in the repo level and still needs to be fixed for all the other primitives

option 3: installation in user level
the expected behavior is that the folder goes directly under .copilot/ folder however the files are installed both under .copilot/ folder and under \AppData\Roaming\Code\User\globalStorage\amadeusitgroup.prompt-registry\bundles\coaching-prompt which is problematic plus the logs only show that the installation happen under \AppData\Roaming\Code\User\globalStorage\amadeusitgroup.prompt-registry\bundles\coaching-prompt which needs to be fixed

Steps to Reproduce

1-installing the collections with the three options.

Expected Behavior

the collections should under the proper folder when installed

Actual Behavior

the collections are under AppData\Roaming\Code\User\globalStorage\amadeusitgroup.prompt-registry\bundles\coaching-prompt for .github installation and under both AppData\Roaming\Code\User\globalStorage\amadeusitgroup.prompt-registry\bundles\coaching-prompt and .copilot/folder for user installation

Error Logs

Operating System

Windows

VS Code Version

1.108.0

Extension Version

0.0.27

Registry Source Type

Awesome Copilot

Additional Context

No response

[wherka-ama]

@Driss-Lalami99 : careful with the user level please. Bundle location is not quite the same as installation. We use global storage as a central place to keep the bundles in their original form. Then you have a process of installing them into a target location, so they are seen by the tools. I reckon the same applies to repo level. It is always a two step process.
What is important, is whether all the files make it to their destination I. A correct form, and in the case of repo level installation, if they are properly registered in the lock file.
I think we need a bit more thorough analysis on this one. I'm not sure at this stage if we should treat it as a bug.

[wherka-ama]

@Driss-Lalami99 : I'm being a bit cheeky here and assigned this bug to you to for the extended analysis and the fix if you'd like to ship one. I hope you don't mind ;-) Thanks in advance ❤️

[Driss-Lalami99]

Hello @wherka-ama, so if my understanding is correct the bundle is installed under \AppData\Roaming\Code\User\globalStorage\amadeusitgroup.prompt-registry\bundles\coaching-prompt and then the installation should be under the specified location for repo level .github/ and for user level .copilot/ if this is the case then there is still an issue for the repository level installation as it does not install them under .github/ and we should also modify the logs to clarify the installation process more, I can take care of this, once you confirm to me that indeed that my understanding is correct !

thank you Waldek ❤️!

[wherka-ama]

Hello @wherka-ama, so if my understanding is correct the bundle is installed under \AppData\Roaming\Code\User\globalStorage\amadeusitgroup.prompt-registry\bundles\coaching-prompt and then the installation should be under the specified location for repo level .github/ and for user level .copilot/ if this is the case then there is still an issue for the repository level installation as it does not install them under .github/ and we should also modify the logs to clarify the installation process more, I can take care of this, once you confirm to me that indeed that my understanding is correct !

thank you Waldek ❤️!

The bundles are indeed extracted/cached in the global storage of the vscode. Then we have a process that either creates symlinks to the "user-level prompts location" which is specific to the platform or simply copied over(installed) into repository level .github. When the resources are installed into repository level, there is no links(or there should be no links) in play as it would be simply silly to let the user commit such links and hope that it will work when such repository is cloned elsewhere.
In this case the entire content of the bundle along with the lock file needs to be present in the repo.

Thank you for your contributions @Driss-Lalami99 !