Adding veto for link fault and changing max_faults to 200

[jyotiphy]

Description

Adding veto for link fault and changing max_faults to 200

Motivation and Context

During beamtime, it was found that link faults aren't vetoed by stopper
And MAX_faults was 100

How Has This Been Tested?

not yet

Where Has This Been Documented?

no

Screenshots (if appropriate):

Pre-merge checklist

• Code works interactively
• Code contains descriptive comments
• Test suite passes locally
• Libraries are set to fixed versions and not Always Newest
• Code committed with pre-commit (alternatively pre-commit run --all-files)

[ZLLentz]

I think this is a strictly positive change

A few more things to note:

• I think the i_xOK veto update actually isn't needed, and only was needed because of the FF count. I think the FFO forces a not OK state when it has too many FFs and ignores its own veto, which is why this FF got tripped. But redundancy is OK and maybe even good here.
• We ended up only needing 104 slots. Next week we should do a follow-up PR where we cut down on the number of slots and/or limit the number exposed to EPICS to speed up the boot time. Possibly the most sane is to keep it at 200 but limit the arrays to ~30 and ~115 in EPICS respectively.
• We would have caught this ahead of beam time if we had implemented Better diagnostics for full FFO allocations pmps-ui#90. I've made this a jira ticket as well now at https://jira.slac.stanford.edu/browse/ECS-3964

[ZLLentz]

This is a pretty healthy PV count drop (23542 -> 16838) 👍
If we cut down the pmps too we might get a pretty fast boot time