feat(remote-development): Add netman.nvim

[Uzaaft]

No description provided.

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

[luxus]

does netman make sense without intigrating it into neo-tree?

[Uzaaft]

Yes, it's mentioned in the docs.

[mehalter]

We should also configure the neo-tree integration here as well if neo-tree exists using the optional key.

[mehalter]

LGTM!