Improve copy about antiroll back for FP4
## Summary
The anti rollback copy doesn't mention different Android versions (Google Android R to /e/OS 12 S)
## The problem
**What is the current behavior?**
The anti rollback copy only mentions downgrading the OS and similar versions
**What is the expected correct behavior?**
Add reference to earlier version on of Google Android
## Solutions
**Proposal for revised copy**
Add another example
Example 3:
* Your FP4 runs Google Android -R while /e/OS is now available based on AOSP -S.
* Your FP4 with Google Android has a `Security Patch Level` saying 2022-10-03 or October 3rd, 2022.
* The /e/OS build available says: `/e/OS build : S stable (Security patch: 2022-06-05)`
* In this example, the /e/OS build has an older `Security Patch level` than the origin, so the anti-roll back protection will trigger, even if the /e/OS version runs on a more recent version of AOSP. In this example, you will brick your phone.
@rhunault @manojnair @nothingtohide FYI
issue