fix(set_tags): better tag parsing for hyphens and whitespaces

[celsobenedetti]

Summary

Tweak in the tag parsing in the set_tags prompt editor.
Now:

1. hyphens are replaced with underscores
2. whitespaces are treated as separators between multiple tags

Example

If a user enters something like this in the set_tags prompt:

OFFICE WORK PROJECT-1

before:

:OFFICE WORK PROJECT-1:

after:

:OFFICE:WORK:PROJECT_1:

Related Issues

Closes #1097

Checklist

I confirm that I have:

• Followed the
  Conventional Commits
  specification (e.g., feat: add new feature, fix: correct bug,
  docs: update documentation).
• My PR title also follows the conventional commits specification.
• Updated relevant documentation, if necessary.
• Thoroughly tested my changes.
• Added tests (if applicable) and verified existing tests pass with
  make test.
• Checked for breaking changes and documented them, if any.

[kristijanhusak]

Both hyphen and space are not a valid value for a tag. Unfortunately, Neovim does not allow limiting the characters that are accepted in the input, so anything can be typed in. Emacs does not allow entering a space in the prompt, and for anything that is typed that does not match the regex, it is converted to a single colon.
So for example, if you type in OFFICE-WORK-PROJECT-1 (I replaced spaces with hyphens since it does not allow spaces), it will actually set tags to :OFFICE:WORK:PROJECT:1. If you do multiple invalid characters, like two hyphens, they are converted to single colon.
We can do the same, while also including the space in the check.

[celsobenedetti]

Both hyphen and space are not a valid value for a tag. Unfortunately, Neovim does not allow limiting the characters that are accepted in the input, so anything can be typed in. Emacs does not allow entering a space in the prompt, and for anything that is typed that does not match the regex, it is converted to a single colon. So for example, if you type in OFFICE-WORK-PROJECT-1 (I replaced spaces with hyphens since it does not allow spaces), it will actually set tags to :OFFICE:WORK:PROJECT:1. If you do multiple invalid characters, like two hyphens, they are converted to single colon. We can do the same, while also including the space in the check.

Went for this approach: celsobenedetti@98d6fdb