Update vendored angle to FIREFOX_140_12_0esr_RELEASE

[jschwe]

Followed the instruction from the readme, deleting gfx/angle and then
re-vendoring by copying the gfx/angle directory from the (firefox) upstream 140.12.0 ESR
firefox release (commit f802561).
See the individual commits.

Companion PR: servo/servo#46455

[sagudev]

I am not sure it's enough to do just patch release here, given that we reexport many stuff from bindgen. Did you check that we are in fact semver compatible (we have much more stuff exposed on windows btw)?

Anyway, maybe we should be doing like in mozjs tracking and automating version bumps? Our LTS release follows firefox ESR I presume (mainly for SM and mozangle, but I guess that would could also work for WR and stylo as both can get security updates from upstream - should we make sure we are properly synchronized to ESR branch for the time of LTS release so that backporting is easier).

[jschwe]

I was going to say it appears to be additive, but cargo semver-checks does complain:

A pub struct constructible with a struct literal has a new pub field. Existing struct literals must be updated to include the new field.

So, I guess a nice reminder for me that a change looking additive can still be breaking.

[sagudev]

this PR needs companion PR in servo, we especially need to test windows builds

[jschwe]

Companion PR servo/servo#46455. I also tested locally on a windows machine, and servoshell seemed to work fine.

[jschwe]

@sagudev could you do a new crates.io release when you have time?

[sagudev]

Published!