feat(pack): Add purescript pack

[srghma]

📑 Description

ℹ Additional Information

[github-actions]

Review Checklist

Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:

Proper conventional commit scoping:

• If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin

• If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error

• Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above

• README is properly formatted and uses fenced in links with <url> unless they are inside a [title](url)

• Entry returns a single plugin spec with the new plugin as the only top level spec (not applicable for recipes or packs).

• Proper usage of opts table rather than setting things up with the config function.

• Proper usage of specs table for all specs that are not dependencies of a given plugin (not applicable for recipes or packs).

[Uzaaft]

PR is in poor state so I am going to mark this as a draft. Please see comments

[srghma]

Currenly wip, blocked by https://github.com/srghma/nvimmer-ps

https://github.com/srghma/nvimmer-ps doesnt have Pimport, Papply, case split etc from https://github.com/shivamashtikar/vimmer-ps and https://github.com/nwolverson/vscode-ide-purescript?tab=readme-ov-file#case-split

https://github.com/srghma/nvimmer-ps idea is to rewrite them on lua, add these futures and not duplicate AstroNvim/astrolsp

[srghma]

@Uzaaft I have finished