Resolve Bug 40418: Update components for switch to mozilla96-based Fenix

superseded by !406 (merged)

context

• this needs a LOT of git cleanup. opening this as draft, and will open another MR to supersede it with squashed fixups, elimination of not-for-merge commits, and some attempt to sort 37659eaf into the appropriate "part" commits

changed the description

added 1 commit

• 8e733658 - fixup! (not for merge) local and/or temporary changes

Compare with previous version

marked this merge request as draft from aguestuser/tor-browser-build@8e733658

added 1 commit

• 0c3d37f4 - fixup! (not for merge) local and/or temporary changes

Compare with previous version

added 1 commit

• bcf26477 - fixup! (not for merge) local and/or temporary changes

Compare with previous version

added 1 commit

• 57eb0640 - fixup! (not for merge) local and/or temporary changes

Compare with previous version

assigned to @aguestuser

requested review from @sysrqb

assigned review to @sysrqb . cc also: @boklm , @richard

added 1 commit

• ea9da25f - fixup! (not for merge) local and/or temporary changes

Compare with previous version

changed the description

added 1 commit

• 3eea3edb - fixup! (not for merge) local and/or temporary changes

Compare with previous version

resolved all threads

mentioned in merge request !406 (merged)

superseded by !406 (merged)

closed

@sysrqb whoops, i neglected to omit this from "clean" version of "android-component part" commit in !406 (merged)

should i:

1. push a fix-up commit to my mozilla96-clean branch on which that MR is based (and make yet-another MR after review in which it has been autosquashed?)
2. autosquash locally and force push onto that MR's branch right now?

i know that (1) is generally our preference, but given small size of the change and trying to get v96 over the line, seemed possibly acceptable?

lemme know!

mentioned in issue #40433 (closed)