mini DR: prefixes

[AlexanderLanin]

Should external needs be referenced by a PREFIX_?

Keep prefixes:

• we can easily guarantee uniqueness of needs across S-CORE.
• we've started that way. Changing that means informing everyone.
• whether an element or local or not is visible by the id.
• sooner or later there will be a conflict
• we can incorporate other needs projects that do not follow S-CORE naming conventions without any conflicts.

Remove prefixes:

• simpler usage.
• Few people actually use docs-as-code at the moment, so it's still easy to change.
• simpler implementation of "combo build" (name pending)
• uniqueness of needs should be guaranteed by naming conventions, e.g. every structural element has some part of the feature tree, component acronym within the id.

[masc2023]

I used prefixes and agree on the advantages. I do not see, that is difficult to use and I do like to not take care, that is unique. I would prefer to stay with it.