What problem does this feature solve?

Among many dependencies, they mark the scope of the dependency as span, range, or start&end. This behavior is very chaotic in Dependency.

This 0-based range is based on the 1-based SWC's Span conversion, and I think we should name it range which used in webpack to avoid ambiguity.

In addition, I think it may be better to name the types of loc and range as DependencyLocation and DependencyRange.

What's your opinion? @h-a-n-a

What does the proposed API of configuration look like?

pub struct Dependency {
  loc: DependencyLocation,
  range: DependencyRange
}

### Tasks
- [ ] https://github.com/web-infra-dev/rspack/issues/7336
- [ ] https://github.com/web-infra-dev/rspack/pull/7576
- [ ] https://github.com/web-infra-dev/rspack/pull/7635
- [ ] https://github.com/web-infra-dev/rspack/pull/7641
- [ ] https://github.com/web-infra-dev/rspack/pull/7671
- [ ] https://github.com/web-infra-dev/rspack/pull/7841
- [ ] https://github.com/web-infra-dev/rspack/pull/7871
- [ ] https://github.com/web-infra-dev/rspack/pull/7892