feat(main): Add type hints to all opts usage for catppuccin/nvim. Catch bug in opts usage for catppuccin

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

is this title still okay? feat(main) didn't passed the "Conventional Commit Title (pull_request_target)" @Uzaaft

[Uzaaft]

is this title still okay? feat(main) didn't passed the "Conventional Commit Title (pull_request_target)" @Uzaaft

We’ve used feat(main) before. I was just waiting on mehalter coming back from his vacay. feat(catppuccin) is def wrong

[luxus]

i checked the possible options feat(colorscheme): is fine.. is this fitting enough? @Uzaaft @mehalter

[Uzaaft]

i checked the possible options feat(colorscheme): is fine.. is this fitting enough? @Uzaaft @mehalter

Let it stay as is.

[mehalter]

well now that I think about it, this probably should have just been docs or something rather than feat since this doesn't change anything about the functionality and just provides documentation of the types in lua 🤷🏼

[Uzaaft]

Should we edit the commit text? @mehalter

[mehalter]

Nah 😂 not bad haha