Move not UI-related torbutton.js code to modules

torbutton_init() is the entry point: we should start there, find out which code does not need to be loaded for every window and move it to a new or existing component.

Trac:
Parent Ticket: legacy/trac#28745 (moved)

moved from torbutton#30850 (moved)

added component::applications/tor browser in Legacy / Trac gitlab-tb-torbutton in Legacy / Trac owner::tbb-team in Legacy / Trac parent::28745 in Legacy / Trac priority::medium in Legacy / Trac severity::normal in Legacy / Trac status::new in Legacy / Trac tbb-torbutton in Legacy / Trac type::defect in Legacy / Trac labels

Add magic gitlab keyword.

Trac:
Keywords: N/A deleted, gitlab-tb-torbutton added

moved from legacy/trac#30850 (moved)

added Bug label and removed 1 deleted label

removed 1 deleted label

added Icebox label

changed milestone to %Sponsor 131 - Phase 5 - Ongoing Maintenance

marked this issue as related to #40938 (closed)

added Sponsor 131 label

added Backlog label and removed Icebox label

removed Backlog label

added Roadmap::Future label

/cc @pierov torbutton thing

removed Bug label

added Task label

added All Platforms label

marked this issue as related to #41700

assigned to @pierov

changed title from Move not UI-related torbutton.js code to XPCOM component/service to Move not UI-related torbutton.js code to modules

removed Roadmap::Future label

added Doing label

added Next label and removed Doing label

added Backlog label and removed Next label

added Next label and removed Backlog label

added Doing label and removed Next label

mentioned in issue #40939 (closed)

marked this issue as related to tor-browser-build#40901 (closed)

closed

removed All Platforms label

added Desktop label

removed Doing label

marked this issue as related to tor-browser-build#40965 (closed)