chore(deps): bump i_overlay from 4.0.6 to 6.0.0

[dependabot]

Bumps i_overlay from 4.0.6 to 6.0.0.

Release notes

Sourced from i_overlay's releases.

v6.0.0

Migration: FloatPointCompatible now uses an associated scalar type

FloatPointCompatible no longer takes the scalar as a generic parameter. Implementations should define type Scalar instead.

Before:

impl FloatPointCompatible<f32> for MyPoint {
    fn from_xy(x: f32, y: f32) -> Self { ... }
    fn x(&self) -> f32 { ... }
    fn y(&self) -> f32 { ... }
}

After:

impl FloatPointCompatible for MyPoint {
    type Scalar = f32;
fn from_xy(x: f32, y: f32) -> Self { ... }
fn x(&self) -> f32 { ... }
fn y(&self) -> f32 { ... }

}

Public float overlay APIs were simplified accordingly. Types that previously carried both point and scalar generics now generally use only the point type, with scalar values expressed as P::Scalar.

v5.0.0

Starting with 5.0.0, i_overlay follows SemVer release cycles.

Changes

• Switched release policy to SemVer.
• Added cargo-semver-checks to CI.

v4.5.0

Changes

• Changed: Reworked buffering algorithm. Now it's relay on default boolean overlay graph. Old legacy buffering overlay graph removed. New algorithm must be more precision stable and safe.
• Added: Unit tests.

v4.2.1

Changes

• Changed: License updated from MIT to dual MIT OR Apache-2.0.
• Added: Integration tests.

v4.2.0

Changes

... (truncated)

Commits

• 34bf825 fix dep
• c1dad91 Merge pull request #73 from iShape-Rust/feature/float_point_compatible
• 98b6e39 more api adjust
• ead6e63 adjust api to new FloatPointCompatible
• fc15109 Merge pull request #71 from iShape-Rust/feature/semver
• d75b418 migrate to semver release cycles
• e564dc7 Merge pull request #68 from iShape-Rust/feature/code_refactoring
• aa196d2 Merge branch 'main' of github.com:iShape-Rust/iOverlay into feature/code_refa...
• 9455812 Merge pull request #67 from iShape-Rust/feature/outline_tests
• 4a9b48f performance fix
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)