Bug 2066924: use 136.0 as the last-watershed for linux-aarch64 on the release channel r=releng-reviewers,jcristau

136.0b6 is _technically_ the most correct version, I guess, because it's the first one we shipped, and updates could theoretically be done from that version to an RC. In practice this probably doesn't happen, and the `compare-directories.py` doesn't support the scenario. Additionally, it's probably better to test an old version on the release channel than on the beta channel, as there is a much greater chance of updates actually happening from 136.0 -> latest.

Differential Revision: https://phabricator.services.mozilla.com/D321727

Author: bhearsum

taskcluster/kinds/test-update-integrity/kind.yml

@@ -147,7 +147,7 @@ tasks:
                         default:
                             by-build-platform:
                                 linux64-aarch64.*:
-                                    version: "136.0b6"
+                                    version: "136.0"
                                 mac.*:
                                     version: "109.0.1"
                                 win.*: