Create unique README across all projects

[endriu3314]

Linked to it-pebune/ani-research-backend#57

Proposal

Follow a unique style README across all projects, including the same workflow and issue template.

Labels

Modify the current labels to the following:

• bug #d73a4a: Something is wrong (used for issues)
• dependencies #0366d6: Issue that warns about dependencies / PR that updates dependencies
• documentation #bfd4f2: Issue/PR that updates documentation
• feature #5319e7: PR that adds a feature to the application
• fix #d93f0b: PR that fixes an existing issue
• hotfix #b60205: PR that fixes an urgent issues (deploys directly to production)

Still keep:

• enhancement, help wanted, good first issue, duplicate, wontfix

Branches & Contributing

Branches

Proposing two default branches:

• main - Staging (ex development)
• prod - Production (ex master)

Every feature/fix will be merged stashed into main.
Main will be merged with all commits to prod.

Rules

Add the following branch protection rules:
For main:

• Require a pull request before merging
  • Require approvals - min 1
• Require status checks to pass before merging
  • Require branches to be up to date before merging
  • When adding tests, require tests to pass
• Require conversation resolution before merging
• Require lienar history

For prod:
Same as main but add following:

• Dismiss stale pull requests approvals when new commits are pushed
• Include administrators

Tags

Follow a clear workflow when contributing, using the same branch tags:

• - feature/branch-name - New feature from main
• - fix/branch-name - New fix from main
• - hotfix/branch-name - New fix from prod (deployed directly, skips staging)

Workflow

• Get assigned an issue
• Create a new branch conform with the Tags
• Create a PR pointing to either main or prod
• Review & Publish