Go to RunningDegraded based on FM conditions

[kakwok]

We primarily go to RunningDegraded based on the active alarms from the alarmer, however, there could be cases where we detect problems in the FM that are not critical enough to goToError, but worth notifying the user by going to RunningDegraded. An example of that is not getting the proper SID, which could indicate a DB problem. See discussion in #209.

One idea to do that is to make another thread to check an FMParameter, say ReasonsForDegarded.
Both FMdegradingWatchThread and AlarmerWatchThread may fill that parameter and goToDegraded base on that. If it is not empty, we go to degraded, if it is empty, we get out of degraded.

Details for this scheme can be further discussed, but the idea is to set up a way for FM to set us to RunningDegraded.

[kakwok]

Following discussion on allowing maskedapps in global runkeys (40df1bc), we want to degrade in global when we use this feature.
We should think about more on how to incorporate two sources for RunningDegraded inputs