Feature Request: Configuration Option for Error Sensitivity Levels

Description

Add a configuration option that allows users to specify what should be considered an error when detecting package version conflicts. This will provide flexibility for different project requirements and tolerance levels.

Proposed Configuration Options

The tool should support the following sensitivity levels:

• Major versions only: Only flag conflicts when different major versions of the same package are detected (e.g., 1.x vs 2.x)
• Minor versions: Flag conflicts when different minor versions are detected (e.g., 1.1.x vs 1.2.x)
• Patch versions: Flag conflicts for any version differences, including patch versions (e.g., 1.1.1 vs 1.1.2)

Implementation Considerations

• This could be implemented as a command-line argument (e.g., --error-level major|minor|patch)
• Default behavior should be configurable
• Should work with the existing dependency analysis pipeline

Use Cases

• Strict environments: Some teams may want to be alerted about any version differences
• Flexible environments: Others may only care about major version conflicts that could introduce breaking changes
• Legacy projects: Projects with many dependencies might want to focus only on major version conflicts initially

Acceptance Criteria

• Command-line option to specify error sensitivity level
• Support for major, minor, and patch level detection
• Clear documentation on what each level detects
• Backward compatibility with existing behavior