ACTIONX: mark GRUPTARG, GSATINJE, GSATPROD and TEST as unsupported

[lisajulia]

• Remove GRUPTARG, GSATINJE and GSATPROD from list of supported keywords by ActionX since they are not supported by flow, see: https://github.com/OPM/opm-simulators/blob/96132fefcf0275a7d6b87de6a5b6e4cc0cb25ed7/opm/simulators/utils/UnsupportedFlowKeywords.cpp#L248, https://github.com/OPM/opm-simulators/blob/96132fefcf0275a7d6b87de6a5b6e4cc0cb25ed7/opm/simulators/utils/UnsupportedFlowKeywords.cpp#L249 and https://github.com/OPM/opm-simulators/blob/96132fefcf0275a7d6b87de6a5b6e4cc0cb25ed7/opm/simulators/utils/UnsupportedFlowKeywords.cpp#L256
• Remove TEST since this is not a keyword

[lisajulia]

jenkins build this please

[blattms]

Nice catch. Thanks.

[blattms]

Was this needed for PYACTION?

The reason for asking is that there should already be an error for ACTIONX, at least once the action is evaluated. But maybe that is too late? What is the current behavior?

There is one small danger: If those keywords get supported then we might still miss them here.

[bska]

For what it's worth all of these were added–by the original author–in PR #2677. Although not discussed in that PR, I do think that the intention was for these to be supported in ACTIONX mode.

[lisajulia]

Was this needed for PYACTION?

The reason for asking is that there should already be an error for ACTIONX, at least once the action is evaluated. But maybe that is too late? What is the current behavior?

There is one small danger: If those keywords get supported then we might still miss them here.

This is not directly needed for PYACTION, yet my task here is to activate all keywords that are active for ACTIONX also for PYACTION.
In any case, if any of those keywords gets supported in the future, we should not just silently activate it for ACTIONX but add and only activate it afterwards.

[lisajulia]

jenkins build this please