Remove potentially misleading "(limited)" for Android

This removes "(limited)" from the description of the `justfile`
recipe `cross-test-android`. It *is* very limited, but that label
is misleading, since currently `cross-test-s390x` (as well as other
`cross` testing targets that could be run through the parameterized
`cross-test` recipe) are limited in all the same ways.

In particular, we are not currently testing them with any external
components built for the target architecture. For example, `git`
built for the host has been upgraded in the container and the
environment has been configured so `gix-path`, `gix-testtools`,
any test cases throughout the workspace can use it without problems
(either directly or through a shell).

In the future, some `cross` targets may gain a richer target
environment to interact with when testing, by installing target
builds of `git`, by installing target builds of libraries that
facilitate more features than `max-pure`, or in other ways. At that
point, convenience recipes for specific targets in the `justfile`
that are more limited than other targets could be marked "(limited)".

Author: EliahKagan

justfile

@@ -236,7 +236,7 @@ cross-test target: (cross-image target)
 # Test s390x with `cross`
 cross-test-s390x: (cross-test 's390x-unknown-linux-gnu')
 
-# Test Android with `cross` (limited)
+# Test Android with `cross`
 cross-test-android: (cross-test 'armv7-linux-androideabi')
 
 # Run cargo-diet on all crates to see that they are still in bound