File::Copy is not supposed to be able to move directories, only single
files. It only works by chance if the source and destination are on
the same filesystem and a rename is working.

Bug 40169: Update apt package cache after calling pre_pkginst, too

The creation of some project containers require an updated apt cache
before executing pre_pkginst, while others require updating the apt
cache after executing pre_pkginst.

While the addition is done in tor-browser#33803, here we just remove the
key related things in tor-browser-build.

Versions bump and Changelog update

This reverts commit 09aff7d7.

Bug 40147: Remove workaround for core/tor#40172 once we pick up 0.4.5.2-alpha

Thanks to boklm for the suggestion in #23631

A pom file of hosted third-party dependencies may be modified at any
time after publication. These files contain metadata about a version of
a repository. We avoid computing and verifying the hash of downloaded
.pom files that are listed in a project's gradle-dependencies-list.txt
because they change unpredictably. This should be safe while the .pom
file is not modified in such a way that it is rejected by gradle and
while we still check the hash of non-.pom files.

The jvnet-parent-*.pom files got slightly updated without the respective
version numbers getting incremented.

The proguard-gradle and httpcomponents-parent-10 .pom files got mainly
reformatted without a version number bump as well.

Our offline builds are busted with Nimbus SDK landing as submodule. See:
https://github.com/mozilla/application-services/issues/3732. We work
around that by pointing to the local viaduct* crates.

We need to add kotlinx-coroutines-android-1.3.9.jar manually, see:
tor-browser-build#40056.

The jvnet-parent-*.pom files got slightly updated without the respective
version numbers getting incremented.

The proguard-gradle and httpcomponents-parent-10 .pom files got mainly
reformatted without a version number bump as well.

Gradle versions change more frequently compared to other toolchain
parts. We don't want to rebuild the whole toolchain and subsequently all
projects just because the Gradle version for one project has changed.
We therefore start with creating an own, separate Gradle project where
all the respective Gradle versions needed by different projects are
fetched and prepared.

Gradle versions still present in `android-toolchain` will move over to
this new project in later commits.

We start with Gradle 6.5 as that is used for `application-services` now.

We need to make sure that we are actually using Java 1.8, otherwise the
build breaks.

The jaxb-parent-2.2.11.pom update is needed as it seems someone fixed
the line endings of that .pom file and replaced the one we had used in
previous dependency lists.

We need to bump Rust to 1.47.0

Mozilla builds their CI and shipped code with Rust SIMD enabled
(see: https://bugzilla.mozilla.org/show_bug.cgi?id=1578677#c4). We
should therefore do the same. Thanks to a cypherpunk for pointing that
out.

Versions bump and Changelog update