score/scope_exit: Define component requirement and clean up test-to-requirement traceability

The `scope_exit` component currently has no component requirement defined.

Previously, `comp_req__utils__scoped_operation` was placed under the utils component, but the implementation (ScopeExit class) lives in [scope_exit](https://github.com/eclipse-score/baselibs/tree/main/score/scope_exit)

The requirement needs to be moved to the correct location and a proper component requirement defined for scope_exit

Apart from that the Component Architecture needs to be defined. The scoped_operation is removed from the Utils lib.

Guidelines for defining component requirements:
https://eclipse-score.github.io/process_description/main/process_areas/requirements_engineering/guidance/requirements_guideline.html

## Traceability

Once the component requirement exists, also apply the test-to-requirement traceability clean-up described in #522 to `scope_exit`.

Start by inspecting the scope_exit component and the Utils library, focusing on the ScopeExit class and the former comp_req__utils__scoped_operation requirement. Read the requirements guideline and issue #522 for the expected component architecture and test-to-requirement traceability format. Done means scope_exit has its own component requirement and architecture, the requirement is removed from Utils, and traceability is cleaned up.

Written by the indexing model from the issue text.