[FEATURE REQUEST] Migrate to trunk based development

### I have searched through the issues and didn't find my problem.

- [X] Confirm

### Problem

Currently we are using a workflow similar to GitFlow and have two major branches: `master` and `develop`.

This causes a lot of overhead when it comes to releases, and can make things overly complicated.

### Possible Solution

A much simpler approach would be to just have a single `master` or `main` branch, and merge all PR's into that. Then once we have something shippable all we have to do is run a workflow to make the release.

### Additional information

In order to make the transition to trunk based development there's a large amount of automation scripts that need to be modified. The good thing is that there will also be quite a few that we can get rid of entirely. For example the [in-develop-labeler](https://github.com/devicons/devicon/blob/master/.github/workflows/in_develop_labeler.yml).
Going to a trunk based development model will drastically improve our agility, and reduce the project's complexity