Templates improvements

[MFK-18]

feat:Update of the system definition acc. to what was in Conflunence for DBS Ref. Edited the macros just to fit the filters for diagrams.

[github-actions]

The pull request does not conform to the conventional commit specification. Please ensure that your commit messages follow the spec: https://www.conventionalcommits.org/.
We also strongly recommend that you set up your development environment with pre-commit, as described in our CONTRIBUTING guidelines. This will run all the important checks right before you commit your changes, and avoids lengthy CI wait time and round trips.

This is the commit validation log:

⧗   input: FEAT: Improved system definition template acc. to DBS ref standard and edited common_macros for diagram filter option and no-content text editing
✖   subject must not be longer than 72 characters [subject-max-length]
✖   type must be one of [build, chore, ci, docs, feat, fix, merge, perf, refactor, revert, test] [type-enum]

✖   found 2 problems, 0 warnings
ⓘ   Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint

⧗   input: FEAT: Updated system functions template with functional exchanges(according to viktors comment)
✖   subject must not be longer than 72 characters [subject-max-length]
✖   type must be one of [build, chore, ci, docs, feat, fix, merge, perf, refactor, revert, test] [type-enum]

✖   found 2 problems, 0 warnings
ⓘ   Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint

⧗   input: commit message
✖   subject may not be empty [subject-empty]
✖   type may not be empty [type-empty]

✖   found 2 problems, 0 warnings
ⓘ   Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint

Here are some examples of valid commit messages:

build: Bump dependency versions
docs(user): Add model creation workflow
feat: Add a monitoring dashboard