Remove invalid sec analysis and correct aou template

[aschemmel-tech]

During usage of templates the following was detected (repaired with this PR):

• feature security_analysis template had wrong content (still has to be defined in Improvement: Open topics in Security Analysis process_description#409)
• AoU templates had no document header (so could not be linked as work product)
• security plan template had duplicate work product "release note"
• add missing safety plan WP link

[github-actions]

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run --lockfile_mode=error //:license-check

Status: ⚠️ Needs Review

Click to expand output

[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.6.0) and connecting to it...
INFO: Invocation ID: c3b97929-e513-4a94-b301-b0393289a4af
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Loading: 1 packages loaded
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)

Analyzing: target //:license-check (39 packages loaded, 10 targets configured)

Analyzing: target //:license-check (78 packages loaded, 10 targets configured)

Analyzing: target //:license-check (87 packages loaded, 10 targets configured)

Analyzing: target //:license-check (138 packages loaded, 1902 targets configured)

Analyzing: target //:license-check (156 packages loaded, 4901 targets configured)

Analyzing: target //:license-check (162 packages loaded, 8132 targets configured)

Analyzing: target //:license-check (163 packages loaded, 8151 targets configured)

Analyzing: target //:license-check (163 packages loaded, 8151 targets configured)

Analyzing: target //:license-check (163 packages loaded, 8151 targets configured)

Analyzing: target //:license-check (163 packages loaded, 8151 targets configured)

Analyzing: target //:license-check (164 packages loaded, 8151 targets configured)

Analyzing: target //:license-check (167 packages loaded, 10160 targets configured)

Analyzing: target //:license-check (168 packages loaded, 10280 targets configured)

Analyzing: target //:license-check (168 packages loaded, 10280 targets configured)

Analyzing: target //:license-check (168 packages loaded, 10280 targets configured)

Analyzing: target //:license-check (168 packages loaded, 10280 targets configured)

INFO: Analyzed target //:license-check (169 packages loaded, 11859 targets configured).
[10 / 16] Creating runfiles tree bazel-out/k8-opt-exec-ST-d57f47055a04/bin/external/score_tooling+/dash/tool/formatters/dash_format_converter.runfiles [for tool]; 0s local ... (2 actions, 1 running)
INFO: From Generating Dash formatted dependency file ...:
INFO: Successfully converted 2 packages from Cargo.lock to bazel-out/k8-fastbuild/bin/formatted.txt
[14 / 16] JavaToolchainCompileBootClasspath external/rules_java+/toolchains/platformclasspath.jar; 0s disk-cache, processwrapper-sandbox
[15 / 16] Building license.check.license_check.jar (); 0s disk-cache, multiplex-worker
INFO: Found 1 target...
Target //:license.check.license_check up-to-date:
  bazel-bin/license.check.license_check
  bazel-bin/license.check.license_check.jar
INFO: Elapsed time: 206.771s, Critical Path: 2.36s
INFO: 16 processes: 12 internal, 3 processwrapper-sandbox, 1 worker.
INFO: Build completed successfully, 16 total actions
INFO: Running command line: bazel-bin/license.check.license_check ./formatted.txt <args omitted>
usage: org.eclipse.dash.licenses.cli.Main [-batch <int>] [-cd <url>]
       [-confidence <int>] [-ef <url>] [-excludeSources <sources>] [-help] [-lic
       <url>] [-project <shortname>] [-repo <url>] [-review] [-summary <file>]
       [-timeout <seconds>] [-token <token>]

[masc2023]

Instead of removing, should we not keep it as empty placeholder for the future?

[aschemmel-tech]

left the folder to align with what is done in component level

[github-actions]

The created documentation from the pull request is available at: docu-html

[masc2023]

Instead of removing, should we not keep it as empty placeholder for the future?

[aschemmel-tech]

left the folder to align with what is done in component level