feat(project): add ProjectMgr plugin

[KenroLe]

Heres another one 🧑‍🌾

[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)

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

[mehalter]

This is awesome! Although I do think this will fit better in the project category that we have (more evidence for the upcoming refactor we want to do to allow multiple categories for plugins...)

[KenroLe]

Oh, i forgot to rename the pr

[mehalter]

LGTM!

[mehalter]

oh shoot, I just realized naming issue. It should be projectmgr-nvim. I'll fix the commit

[mehalter]

@KenroLe just a heads up, the name of the folder should be the entire repository name with the . replaced with - so projectmgr.nvim would be projectmgr-nvim. I revised the commit :)