chore: issue labeling and format

[kaljarv]

Some questions:

• backend/frontend
• do we need personas
• check other repos

[norppaa]

Some good ideologies:

• Labels Should not be used excessively *One PR or issue should only be flagged with max one of each label type, not for example type:bug, type:chore, type:feature... like it is now
• At least three types of labels: Status, type and priority. In addition, custom label types can be thought of.
• Status should cover the state that an issue is right now, for example abandoned, available, blocked, completed, in progress, on hold etc.
• Type should reflect what type of issue we are dealing with, for example: bug, enhancement, maintenance, feature, refactoring. Probably should not include more specific ones: svelte component, svelte page
• Colors should mean something and be distinguishable
• Status and priority can also be pictured using the scrum boards feaatures, but this is project specific and won't probably be visible in PRs. We could alternatively use labels as well, but mixing does not work.

https://medium.com/@dave_lunny/sane-github-labels-c5d2e6004b63

Our case:

• Now type and category sometimes overlap. The division between these two should be made more clear. They are useful when used together, for example: type: bug category: security both of them can also be used separately
• Tag seems useful. However, I am wondering if it overlaps with status. If status only contains labels listed above, tag could provide additional info, for example: good first issue, help wanted, invalid, question. Then they could be used together like this: status: in progress tag: help wanted or status: available tag: question or both of them could be used separately
• I have not found any repos that use personas. I think they can sometimes provide useful information, but now they mainly offer mixed info and the purpose is not clear. At the moment it seems like category and persona overlap in some cases. Maybe the personas would be more clear if the labels indicated for which side the issue is targeted for, for example admin, candidate, voter, developer. I am not entirely sure what the meaning behind persona is atm.

[kaljarv]

• Kill Personas
• Convert tag to status
• Fix colors
• Move away from User Stories
• Scope or smth for voter, candidate and future publisher apps, back/frontend maybe not necessary

[kaljarv]

Depends #558

[kaljarv]

One further thing I forgot was that please update the docs regarding labels at the same time: docs/contributing/how-to-use-labels.md.