fix(clojure): add space after clojure comment character

[practicalli-johnny]

Add comment between ;; comment characters for clojure and text being commented

[mehalter]

@practicalli-john for the scope, and I should clarify this in the contribution guidelines, it should be the name of the already existing folder you are modifying. When you are adding a new plugin it is modifying the categories folder. When you are making changes to an already existing plugin the scope is the name of the plugin. This makes a very nice to read changelog.

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