Platform/RaspberryPi: Update TF-A to v2.5

This is a run-of-the-mill update of the TF-A binaries used by the
Raspberry Pi 3 and Raspberry Pi 4 platforms, based on the recently
released TF-A 2.5.

These binaries were built in an open and verifiable manner through
a GitHub Actions build script (https://github.com/pftf/pitf).

It should be noted that we are only updating the binaries due to the
existing ones getting a bit old, in case some of the ARM erratas and
changes, that have been included in the past two TF-A releases, may
benefit us. However, unless there are changes of direct interest for
the Pi platform, we are not planning to update these binaries for
each TF-A release.

Tested for regression on Pi 3 Model B and Pi 4 Model B.

Signed-off-by: Pete Batard <pete@akeo.ie>
Acked-by: Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>
Acked-by: Ard Biesheuvel <ardb@kernel.org>

Platform/RaspberryPi/RPi3/TrustedFirmware/Readme.md

@@ -2,14 +2,14 @@ ARM Trusted Firmware for Raspberry Pi 3
 =======================================
 
 The `bl1.bin` and `fip.bin` TF-A binaries found in this directory were built from the
-[official TF-A 2.3 release](https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/tag/?h=v2.3)
-through an [AppVeyor build script](https://github.com/pbatard/pitf/blob/master/appveyor.yml)
+[official TF-A 2.5 release](https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/tag/?h=v2.5)
+through a [GitHub build script](https://github.com/pftf/pitf/blob/master/.github/workflows/build.yml)
 that is designed to provide evidence that these binaries match the vanilla TF-A source.
 
-As per the [AppVeyor build log](https://ci.appveyor.com/project/pbatard/pitf/builds/32330098),
+Per the [GitHub Actions log](https://github.com/pftf/pitf/runs/2822874196),
 the SHA-256 sums for the blobs can be validated to be as follows:
-- `bl1.bin`: `28d70adc6e7041582264874d342bcad992adb8d34c9de5813e661029d0189b3b`
-- `fip.bin`: `02a8c3ea9227fbe60ecfc20999db6bb755d0b32fd757a596353e068e1814e171`
+- `bl1.bin`: `5ba701a7e977d308a19928e19937107387677d52a1a4d628a5c2bb4e795aae8b`
+- `fip.bin`: `0c3f8a3e8192e5dcb3bdc5867976e4277e9d948159a92ee71a54e92cb8dce9a3`
 
 For Raspberry Pi 3 usage, TF-A was built using the command:
 ```

Platform/RaspberryPi/RPi4/TrustedFirmware/Readme.md

@@ -2,13 +2,13 @@ ARM Trusted Firmware for Raspberry Pi 4
 =======================================
 
 The `bl31.bin` TF-A binary found in this directory was built from the
-[official TF-A 2.3 release](https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/tag/?h=v2.3)
-through an [AppVeyor build script](https://github.com/pbatard/pitf/blob/master/appveyor.yml)
+[official TF-A 2.5 release](https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/tag/?h=v2.5)
+through a [GitHub build script](https://github.com/pftf/pitf/blob/master/.github/workflows/build.yml)
 that is designed to provide evidence that these binaries match the vanilla TF-A source.
 
-As per the [AppVeyor build log](https://ci.appveyor.com/project/pbatard/pitf/builds/32330098),
+Per the [GitHub Actions log](https://github.com/pftf/pitf/runs/2822874196),
 the SHA-256 sum for the bin can be validated to be as follows:
-- `bl31.bin`: `b868ef51cead73ab96b2af778334eb063f6bc8009736c1a16080edc21796dc6a`
+- `bl31.bin`: `59c4486a0a257c8d630d8ea39d6a13d038cd50be4fc9a81985bf2c32a7c3fca6`
 
 For Raspberry Pi 4 usage, TF-A was built using the command:
 ```