Update verification plan template

[pahmann]

What

Improve the listing of recommended methods in the verification plan template.

Verification Methods
--------------------

This section lists the specific verification methods used, such as static analysis,
dynamic testing, reviews, and inspections. Each method should be briefly described,
including its purpose and applicability at different levels of verification.
Reference tables can list methods, identifiers, applicable levels and ASIL relevance.

Test Derivation Methods
^^^^^^^^^^^^^^^^^^^^^^^

This section details the techniques used to derive test cases (e.g., boundary value analysis,
equivalence partitioning, requirements tracing). It should clarify which techniques are used
at each level of testing and for different ASIL levels.  Again, a reference table is recommended.

This is here: https://eclipse-score.github.io/process_description/main/process_areas/verification/guidance/verification_plan_template.html

The template gives no recommendations what to use, e.g. boundary value analysis for ASIL-B or requirements testing for all.

Acceptance Criteria (DoD)

Aligned to the software verification plan in S-CORE:
https://eclipse-score.github.io/score/main/platform_management_plan/software_verification.html#verification-methods

How

Add a example table as in the verification plan and mark that this serves as an example.