System-interaction: mode-transition dependencies

**SC profile shall specify mode-transition dependencies, if any.**

Rationale: This requirement is a specialization of the requirement “SC profile shall discuss API system-interaction details as much as needed to ensure safety.”

Example: The following are dependencies that can be specified:
- API implementation requires certain modes to be made available by the system;
- API implementation depends on another system component being in a certain mode before the implementation can transition to a mode, such as EGL implementation being in non-safe mode before OpenGL SC implementation can transition from non-safe to safe mode;
- API implementation requires means to be notified by the system if a dependency is violated, such as EGL implementation transitioning from non-safe to safe mode before OpenGL SC implementation.

No file or test is identified in the issue. Start by locating the SC profile requirements and the existing API system-interaction details, then determine where this requirement belongs; done means the profile requirements cover mode availability, dependent component modes, and notification when a dependency is violated.

Written by the indexing model from the issue text.