feat!: Remove melos.yaml in favor of the root pubspec.yaml

[spydon]

Description

Since we now declare the packages in the workspace section in the pubspec.yaml file we'll move the rest of the config in there too, under it's own melos section. This is common practice for other dart tools too and the Dart team knows about it.

Continues on the #747 effort.

Type of Change

• ✨ feat -- New feature (non-breaking change which adds functionality)
• 🛠️ fix -- Bug fix (non-breaking change which fixes an issue)
• ❌ ! -- Breaking change (fix or feature that would cause existing functionality to change)
• 🧹 refactor -- Code refactor
• ✅ ci -- Build configuration change
• 📝 docs -- Documentation
• 🗑️ chore -- Chore

[docs-page]

To view this pull requests documentation preview, visit the following URL:

docs.page/invertase/melos~832

Documentation is deployed and generated using docs.page.

[ricardodalarme]

For some reason I cannot import this version of Melos into my repo:

Error on line 1, column 7: "name" field doesn't match expected name "melos".
  ╷
1 │ name: melos_workspace
  │       ^^^^^^^^^^^^^^^
  ╵
exit code 65

note: the name of my workspace is monorepo.

[spydon]

For some reason I cannot import this version of Melos into my repo:

Error on line 1, column 7: "name" field doesn't match expected name "melos".
  ╷
1 │ name: melos_workspace
  │       ^^^^^^^^^^^^^^^
  ╵
exit code 65

note: the name of my workspace is monorepo.

Interesting, what do you have in your root pubspec.yaml?

[ricardodalarme]

Oh, it was actually a typo in the path, I've just updated it and it works fine now. Srr