Allow export/import of Package Library

[pbalsara-wk]

Is there an existing request for this feature?

• I have searched the existing issues for this feature request and I know that duplicates will be closed

Is your feature request related to a problem?

I was exporting a collection to share with a customer. I had someone else part of my company but not on my team import the collection and they mentioned that the post-scripts weren't working because they didn't have the Package Library. I was disappointed because I've been providing this to external users without knowing that Package Library wouldn't be included. Previously, I would include the script directly within the collection and the customer would not have any issues. However, this is making it harder for external users to integrate to our APIs. Package Library is only accessible to the team and not to external users. We cannot invite external users to our team because they would see all other customer workflows within our Workspace.

Describe the solution you'd like

We use Package Library to capture responses returned in responses. We would like to have package libraries exported along with collection so that when we provide them to external users, the end-to-end API functionality remains intact.

Describe alternatives you've considered

I've considered switching back to just writing the script directly in the API request post-script section itself. It's a lot of copy-pasting since there's no way to export package libraries.

Additional context

No response