Low: scheduler: ignore unknown actions for resource state

Previously, we considered any action other than notify or meta-data to affect
resource state (active and/or failed). This meant that results of unknown
action names in resource history (which should be possible only with manual
editing or a custom recurring action) could potentially affect resource state.

Now, we specifically list the actions that do affect state. This technically
breaks behavioral backward compatibility, though probably not in real-world
scenarios.