Expose a single dedicated entry point for bundle report #153
Description
Title: Expose a dedicated entry point for bundle_report in next_rails
Description:
We’d like to propose exposing a single, dedicated entry point for the bundle_report command to make it easier to invoke programmatically.
Right now, the logic lives directly in exe/bundle_report, which makes reuse and integration in other tools more difficult. Having a consistent CLI entry point (e.g. something like NextRails::BundleReport::CLI.new(ARGV).run
or NextRails::BundleReport.start(ARGV)) would align with how tools like Brakeman and LibYears are structured and improve composability.