feat: add rose pine theme

[basilbarge]

My take on implementing the main Rose Pine theme palette

[gierens]

I renamed the files to rose-pine removing the main, seems unnecessary, at least until we have more than a single rose-pine theme.

I also squashed fixes into the commits that created the corresponding sources and rewrote messages to conform to conventional commit quidelines.

Other than that, LGTM, thanks for the contribution :)

[basilbarge]

Okay awesome. Thanks for the feedback, this is my first time contributing to someone else's public project :)

[gierens]

@basilbarge awesome, congratulations! :)

A couple to tips, because reviewers on other projects can be more demanding of PR authors:

• PR should usually be self-contained but try to make them a small as possible for easier review, you've done that, so perfect ☑️
• stick to small/atomic commits, makes for a cleaner history and squashing commits is easier than picking them apart, you also did that, great ☑️
• get familiar with rewriting your commits, git reset, git commit --amend and particularly git rebase -i. While it's fine to just commit as you go while still developing the PR, it is good practice to cleanup the history once it is ready for review. So for example if commit 1 adds a feature and in commit 4 you fix a typo you made in commit 1, then squashing commit 4 into commit 1 would clean up the history. 🔲
• also sometimes there a contribution guidelines on projects, like using conventional commit style commit messages, that's more my fault that this wasn't done already, because we haven't yet documented it here. 🔲