Add stopFirst option to stop services before running dependencies

[RodrigoHamuy]

Summary

This PR adds a new stopFirst configuration option for script dependencies that allows stopping a running service before executing a dependency. This is useful when a dependency needs to write files that the service currently has open.

Key Changes

• schema.json: Added stopFirst boolean property to dependency configuration with documentation explaining its purpose
• src/config.ts: Added stopFirst: boolean field to the Dependency interface
• src/analyzer.ts:
  • Added parsing logic to read the stopFirst property from configuration
  • Validates that stopFirst is a boolean value, reporting errors if invalid
  • Passes the stopFirst value to the dependency configuration
• src/execution/service.ts:
  • Checks if any dependency has stopFirst: true before executing dependencies
  • If so, stops the adoptee (running service) before executing dependencies
  • Ensures the service is only stopped once and handles the case where the service is aborted while waiting for the adoptee to stop

Implementation Details

• The stopFirst option defaults to false to maintain backward compatibility
• When a dependency has stopFirst: true, the service is stopped before that dependency runs, allowing the dependency to freely write to files
• The implementation properly handles async operations and state transitions during the stop/execute sequence

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.