Consider sync committee participation for exiting validators

https://github.com/ethereum/staking-launchpad/blob/2a136b4bc70451cda4c08e2137d35be2201dd179/src/pages/Withdrawals/index.tsx#L760


I think this explanation does not consider an exiting validator being part of the sync committee. [This validator (beaconcha.in)](https://beaconcha.in/validator/8f1e9fcd9d13b531d2a6b53ba9000ef076efc699bd7c2f12949535e30fde3116ee7d092015aa9303bc4b53f7f72e5312#sync) was elected to be part of the sync committee (SC) starting at 201472. Before the SC started, the validator exited at 201320. The validator kept running, was marked withdrawable and was even fully swept 26 epochs before the SC ended. It earned SC rewards throughout the entire SC epochs and there's a partial withdrawal after the full withdrawal and end of the SC.

So this statement from the launchpad does not seems to be accurate, or at least not accurate regarding SC participation, right?
> validator is no longer active, no longer earning rewards

TBH, SC participation is a very rare event for operators and this scenario is probably an edge case. But since it's a very lucrative situation for operators, it might be worth mentioning:
- to keep the validator running if it's part of the current or next SC
- to keep the validator running for 512 (256*2 = 2 SCs) epochs after exiting by default, if the SC participation check is not feasible

What do you think?

Credits to the Figment team for providing the illustration and validator example.