feat: support for melos command within script steps

[jessicatarra]

Description

This pull request introduces support for melos command within script steps, as suggested in issue #653. An example configuration demonstrating this new capability is as follows:

scripts:
  pre-commit:
    description: pre-commit git hook script
    steps:
      - echo 'hello world'
      - format --output none --set-exit-if-changed
      - analyze --fatal-infos

I'll need some help on determining the appropriate range of commands to support. Should we use every command possible?
Currently, the following commands are under consideration:

    const melosCommands = {
      'analyze',
      'format',
      'bs',
      'bootstrap',
      'clean',
      'list',
      'publish',
    };

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

[spydon]

Lgtm!

[spydon]

Aah the pain of Windows, this has to have two backslashes \\

[jessicatarra]

Ohhh I see, hopefully the last commit solves this issue!

[jessicatarra]

for some reason, even though I added the two backslashes, the error seems to be something else @spydon:

              'warning - pubspec.yaml:6:11 - The path \'d:\\a\\melos\\melos\\packages\\melos\' isn\'t a POSIX-style path. Try converting the value to a POSIX-style path. - path_not_posix\n'
              '   info - packages\\a\\main.dart:3:13 - Don\'t invoke \'print\' in production code. Try using a logging framework. - avoid_print\n'
              '   info - packages\\a\\main.dart:5:10 - Missing a newline at the end of the file. Try adding a newline at the end of the file. - eol_at_end_of_file\n'
              '\n'
              '3 issues found.\n'

[jessicatarra]

@spydon I updated the test and use a list script instead of the analyze one to avoid all these issues related to windows environments, and still testing the right scenario, which is prioritazing custom scripts instead of Melos commands when scripts with same names as the commands are used. commit e1d2e96