Adding log frontend requirements

[MaciejKaszynski]

Fixes eclipse-score/logging#192

The log component doesn't have all of the feature requirements linked to component requirements.
Note that log is split into 3 components (log_backends (logging repo), datarouter (logging repo), log_frontend (baselibs repo) so this PR only add component requirements for the log_frontend component of the logging feature.
So this is adding requirements related to the log interfaces and the log configuration loading.

[arsibo]

logging will have 3 components

• log ( frontend) path: baselibs/score/mw/log/ ; baselibs/score/mw/log/rust; baselibs/score/mw/log/cpp (see Relocate Rust source code from src into component folders under score #248 (comment))

• log_backend (logging/score/log_backend )

• datarouter (logging/score/datarouter )

• mw as directory will be discussed by BMW (stateful indicator )

• we need no component architecture, due to missing sub components

[MaciejKaszynski]

logging will have 3 components

* log ( frontend) path: baselibs/score/mw/log/ ; baselibs/score/mw/log/rust; baselibs/score/mw/log/cpp (see [Relocate Rust source code from `src` into component folders under `score` #248 (comment)](https://github.com/eclipse-score/baselibs/issues/248#issuecomment-4853908888))

* log_backend (logging/score/log_backend )

* datarouter (logging/score/datarouter )

* mw as directory will be discussed by BMW (stateful indicator )

* we need no component architecture, due to missing sub components

@arkjedrz I see you created the architecture docs for baselibs_rust/log. Is it fine to remove this since the rust shouldn't be a sub-component?

[MaciejKaszynski]

logging will have 3 components

* log ( frontend) path: baselibs/score/mw/log/ ; baselibs/score/mw/log/rust; baselibs/score/mw/log/cpp (see [Relocate Rust source code from `src` into component folders under `score` #248 (comment)](https://github.com/eclipse-score/baselibs/issues/248#issuecomment-4853908888))

* log_backend (logging/score/log_backend )

* datarouter (logging/score/datarouter )

* mw as directory will be discussed by BMW (stateful indicator )

* we need no component architecture, due to missing sub components

@arkjedrz I see you created the architecture docs for baselibs_rust/log. Is it fine to remove this since the rust shouldn't be a sub-component?

Actually looking more, the arch & detailed design is duplicated so I think deleting the arch and keeping the detailed design would be fine?

[github-actions]

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

[MaximilianSoerenPollak]

All of the requirements should have a version attribute as well.
It is not yet mandatory but will be in the next Docs-As-Code release, so you could save yourself some work by adding it now already

[rmaddikery]

Why not redirect?

[MaciejKaszynski]

The markdown files from the score/ directory are not built into the docs, this is why we need to move them. Do you want me to add a link to the github page? I don't think this would look too nice in docs.