chore: Migrate to Melos 8 with a pub workspace and add the Flame release workflows

.github/.cspell/dart_dictionary.txt

@@ -0,0 +1,5 @@
+# keywords/terms specific to the Dart/Flutter ecosystem
+endtemplate # Use @endtemplate to close a @template block in dartdoc
+LTWH # Left, Top, Width, Height, as in Rect.fromLTWH
+pubspec # dependency and configuration file of every Dart project
+xcworkspace # Xcode workspace file used by Flutter on macOS and iOS

.github/.cspell/mini_sprite_dictionary.txt

@@ -0,0 +1,3 @@
+# dictionary file for Mini Sprite related words, including companies, tools, and libraries mentioned in the codebase
+Bluefire # The team behind Mini Sprite and Flame https://github.com/bluefireteam
+Dashbook # UI development tool for Flutter https://github.com/bluefireteam/dashbook

.github/.cspell/people_usernames.txt

@@ -0,0 +1,2 @@
+# specific people's names and/or usernames
+erickzanardo # github.com/erickzanardo

.github/.cspell/words_dictionary.txt

@@ -0,0 +1,2 @@
+# actual english words (or common abbreviations) missing from CSpell
+unfill # the opposite of fill, used for the editor's unfill tool

.github/FUNDING.yml

@@ -0,0 +1,3 @@
+open_collective: blue-fire
+github: bluefireteam
+patreon: bluefireoss

.github/cspell.json

@@ -0,0 +1,46 @@
+{
+  "version": "0.2",
+  "language": "en",
+  "flagWords": [
+    "teh",
+    "hte"
+  ],
+  "ignorePaths": [
+    "**/art/**",
+    "**/assets/**",
+    "**/CHANGELOG.md"
+  ],
+  "ignoreRegExpList": [
+    "\\#[\\w\\-]+"
+  ],
+  "dictionaries": [
+    "en_US",
+    "softwareTerms",
+    "dart_dictionary",
+    "mini_sprite_dictionary",
+    "people_usernames",
+    "words_dictionary"
+  ],
+  "dictionaryDefinitions": [
+    {
+      "name": "dart_dictionary",
+      "path": "./.cspell/dart_dictionary.txt",
+      "addWords": true
+    },
+    {
+      "name": "mini_sprite_dictionary",
+      "path": "./.cspell/mini_sprite_dictionary.txt",
+      "addWords": true
+    },
+    {
+      "name": "people_usernames",
+      "path": "./.cspell/people_usernames.txt",
+      "addWords": true
+    },
+    {
+      "name": "words_dictionary",
+      "path": "./.cspell/words_dictionary.txt",
+      "addWords": true
+    }
+  ]
+}

.github/pull_request_template.md

@@ -1,23 +1,67 @@
+<!-- Exclude from commit message -->
 <!--
-  Thanks for contributing!
+The title of your PR on the line above should start with a [Conventional Commit] prefix
+(`fix:`, `feat:`, `docs:`, `test:`, `chore:`, `refactor:`, `perf:`, `build:`, `ci:`,
+`style:`, `revert:`). This title will later become an entry in the [CHANGELOG], so please
+make sure that it summarizes the PR adequately.
 
-  Provide a description of your changes below and a general summary in the title
+Don't remove the "exclude from commit message" comments below. They are used to prevent
+the PR description template from being included in the git log.
+Only change the "Replace this text" parts.
+-->
+
+# Description
+<!--
+Provide a description of what this PR is doing.
+If you're modifying existing behavior, describe the existing behavior, how this PR is changing it,
+and what motivated the change. If this is a breaking change, specify explicitly which APIs were
+changed.
+-->
+<!-- End of exclude from commit message -->
+Replace this text.
 
-  Please look at the following checklist to ensure that your PR can be accepted quickly:
+<!-- Exclude from commit message -->
+## Checklist
+<!--
+Before you create this PR confirm that it meets all requirements listed below by checking the
+relevant checkboxes with `[x]`. If some checkbox is not applicable, mark it as `[-]`.
 -->
 
-## Description
+- [ ] I have followed the [Contributor Guide] when preparing my PR.
+- [ ] I have updated/added tests for ALL new/updated/fixed functionality.
+- [ ] I have updated/added relevant documentation and added dartdoc comments with `///`.
+
 
-<!--- Describe your changes in detail -->
+## Breaking Change?
+<!--
+Would your PR require Mini Sprite users to update their apps following your change?
 
-## Type of Change
+If yes, then the title of the PR should include "!" (for example, `feat!:`, `fix!:`). See
+[Conventional Commit] for details. Also, for a breaking PR uncomment and fill in the "Migration
+instructions" section below.
+-->
+
+- [ ] Yes, this PR is a breaking change.
+- [ ] No, this PR is not a breaking change.
+
+<!--
+### Migration instructions
+
+If the PR is breaking, uncomment this header and add instructions for how to migrate from the
+currently released version in-between the two following tags:
+-->
+<!-- End of exclude from commit message -->
+<!-- Exclude from commit message -->
+
+## Related Issues
+<!--
+Indicate which issues this PR resolves, if any. For example:
 
-<!--- Put an `x` in all the boxes that apply: -->
+Closes #1234
+!-->
 
-- [ ] ✨ New feature (non-breaking change which adds functionality)
-- [ ] 🛠️ Bug fix (non-breaking change which fixes an issue)
-- [ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
-- [ ] 🧹 Code refactor
-- [ ] ✅ Build configuration change
-- [ ] 📝 Documentation
-- [ ] 🗑️ Chore
+<!-- Links -->
+[Contributor Guide]: https://github.com/bluefireteam/mini_sprite/blob/main/CONTRIBUTING.md
+[Conventional Commit]: https://conventionalcommits.org
+[CHANGELOG]: https://github.com/bluefireteam/mini_sprite/blob/main/CHANGELOG.md
+<!-- End of exclude from commit message -->

.github/workflows/cicd.yml

@@ -0,0 +1,68 @@
+name: cicd
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    types: [opened, reopened, synchronize]
+
+
+env:
+  FLUTTER_MIN_VERSION: '3.47.0'
+
+jobs:
+  # BEGIN LINTING STAGE
+  format:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: subosito/flutter-action@v2
+      - uses: bluefireteam/melos-action@v3
+      - run: melos run format-check
+
+  analyze:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: subosito/flutter-action@v2
+        with:
+          flutter-version: ${{env.FLUTTER_MIN_VERSION}}
+      - uses: bluefireteam/melos-action@v3
+      - name: "Analyze with lowest supported version"
+        run: melos exec -- dart analyze --fatal-infos .
+
+  analyze-latest:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: subosito/flutter-action@v2
+      - uses: bluefireteam/melos-action@v3
+      - name: "Analyze with latest stable"
+        uses: invertase/github-action-dart-analyzer@v3
+        with:
+          fatal-infos: true
+
+  markdown-lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: actions/setup-node@v7
+        with:
+          node-version: 18
+      - run: npm install -g markdownlint-cli
+      - run: markdownlint . -p .markdownlintignore -c .markdownlint.yaml
+  # END LINTING STAGE
+
+  # BEGIN TESTING STAGE
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: subosito/flutter-action@v2
+        with:
+          cache: true
+      - uses: bluefireteam/melos-action@v3
+      - name: Run tests
+        run: melos run test:select --no-select
+  # END TESTING STAGE

.github/workflows/gh-pages.yml

@@ -0,0 +1,20 @@
+name: Gh-Pages
+
+on:
+  push:
+    branches: [main]
+  workflow_dispatch:
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v7
+      - uses: subosito/flutter-action@v2
+      - uses: bluefireteam/melos-action@v3
+      - uses: bluefireteam/flutter-gh-pages@v9
+        with:
+          workingDir: packages/mini_sprite_editor
+          baseHref: /