feat: add labels config for the repostitory

[zivkovicmilos]

Description

This PR introduces a list of base labels to the repository, that can be managed by the community.

1️⃣ Propose to remove

• dapp
• github_actions (dependencies can mean the same)
• gnoland
• integration
• invalid
• packaging
• enhancement (I believe it’s redundant given other labels)
• core
• chore
• experiments (see list below for alternative)
• tool
• wontfix
• tests* (Not sure about this one, I believe we should include tests with any new functionality we add upstream)

2️⃣ Propose to add

• bug fix - Functionality that fixes a bug
• breaking change - Functionality that contains breaking changes
• don't merge (replaces experiments) - Please don’t merge this functionality temporarily
• feature - New update to Gno
• hotfix - Major bug fix that should be merged ASAP
• info needed - More information needed
• investigating - This behavior is still being tested out

3️⃣ Final list

• bug - Something isn’t working
• bug fix - Functionality that fixes a bug
• dependencies - Update to the dependencies
• documentation - Improvements or additions to documentation
• duplicate - This issue or pull request already exists
• good first issue - Good for newcomers
• help wanted - Extra attention is needed
• breaking change - Functionality that contains breaking changes
• don't merge - Please don’t merge this functionality temporarily
• feature - New update to Gno
• hotfix - Major bug fix that should be merged ASAP
• info needed - More information needed
• question - Questions about Gno
• investigating - This behavior is still being tested out

Changes include

• Bugfix (non-breaking change that solves an issue)
• Hotfix (change that solves an urgent issue, and requires immediate attention)
• New feature (non-breaking change that adds functionality)
• Breaking change (change that is not backwards-compatible and/or changes current functionality)

Checklist (for contributors)

• I have assigned this PR to myself
• I have added at least 1 reviewer
• I have added the relevant labels
• I have updated the official documentation
• I have added sufficient documentation in code

Testing

• I have tested this code with the official test suite
• I have tested this code manually

Additional comments

We can utilize a GitHub action job for each time this labels config is changed.
This would involve defining a specific job with a path filter, and utilizing the GITHUB_TOKEN for managing the repo labels (that's used to authenticate with the tool for managing these labels).