uplift docs-as-code v1.3.0

[nicu1989]

Enables optional_links warnings as info.

Related: #178

[masc2023]

Discussed this already with @AlexanderLanin , your example is great, because this change is not aligned and no wanted from process team, we agreed to decide, what is to be changed in meta model and what in process

does not follow regex:
^std_(wp__iso26262|wp__isosae21434|wp__isopas8926|iic_aspice_40)__.*$

-> Not alinged, will not change now

[masc2023]

See comment

[github-actions]

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

[nicu1989]

Discussed this already with @AlexanderLanin , your example is great, because this change is not aligned and no wanted from process team, we agreed to decide, what is to be changed in meta model and what in process

does not follow regex: ^std_(wp__iso26262|wp__isosae21434|wp__isopas8926|iic_aspice_40)__.*$

-> Not alinged, will not change now

Cool, so then lets leave things unchanged until it is decided what`s to be changed in metamodel and what to be changed in process, right?

[masc2023]

Discussed this already with @AlexanderLanin , your example is great, because this change is not aligned and no wanted from process team, we agreed to decide, what is to be changed in meta model and what in process
does not follow regex: ^std_(wp__iso26262|wp__isosae21434|wp__isopas8926|iic_aspice_40)__.*$
-> Not alinged, will not change now

Cool, so then lets leave things unchanged until it is decided what`s to be changed in metamodel and what to be changed in process, right?

yes, that's why this topic is already on the agenda for next meeting, you are now also invited, that's why the latest release did not upgrade to latest version
https://github.com/orgs/eclipse-score/discussions/407

[masc2023]

Will get a new version with updated metamodel, thus close this PR here
Will be followed-up here, when the new version of Doc-as-code is available
#184