Update crates to use bitflags 0.5

[saurvs]

Part of #10077

---

This change is

[highfive]

Heads up! This PR modifies the following files:

• @bholley: components/style/logical_geometry.rs, components/style/Cargo.toml, components/style/restyle_hints.rs, components/style/element_state.rs
• @KiChjang: components/script/Cargo.toml, components/script/dom/node.rs, components/script/dom/webglrenderingcontext.rs
• @SimonSapin: components/style/logical_geometry.rs, components/style/Cargo.toml, components/style/restyle_hints.rs, components/style/element_state.rs
• @emilio: components/script/dom/webglrenderingcontext.rs

[highfive]

Warning

• These commits modify gfx, layout, style, and script code, but no tests are modified. Please consider adding a test!

[nox]

I don't see any Cargo.lock changes so this is incomplete. Please use ./mach cargo-update -p on bitflags and probably the crates that depend on it.

[metajack]

@bors-servo r+

Looks like the Cargo.lock's got updated.

[bors-servo]

📌 Commit 3d9c1b6 has been approved by metajack

[metajack]

@bors-servo r-

This adds new dependencies but doesn't remove the old ones. There should be only one dependency on bitflags or there should be an explanation here as to why we need 2 or 3 versions of it.

[saurvs]

After I updated all the crates to use bitflags 0.5, I ran ./mach build and then ./mach update-cargo. I guess the old versions of bitflags still remain in some files because the crates that aren't a part of Servo still use an older version of bitflags? If so, they need to be updated for Servo to completely depend on 0.5, and that'll take some more time.

[bors-servo]

☔ The latest upstream changes (presumably #10429) made this pull request unmergeable. Please resolve the merge conflicts.

[nox]

Superseded by #11191.