Clarify cross-cutting concerns vs. cross-cutting concepts

[ulibecker]

Fixes #640
Map cross-cutting concern to aspect and solution concept for a cross-cutting
concern to a cross-cutting concept

[github-actions]

Build Successful! You can find a link to the downloadable artifacts below.

Name	Link
Commit	56e7d91
Logs	https://github.com/isaqb-org/curriculum-foundation/actions/runs/11321819394
Download	https://github.com/isaqb-org/curriculum-foundation/suites/29574221384/artifacts/2051601581

[gernotstarke]

You introduce a new term aspect, which I cannot map to an existing term/concept in the curriculum. I doubt that this new term is neccessary or useful... please let us discuss that in the corresponding issue first.

[ulibecker]

The term "aspect" was already present in the curriculum: "typical cross-cutting concerns (synonym: cross-cutting concepts, aspects)..."

[rhoadesre]

Looks good.

[rhoadesre]

Propose to corresponding changes in LG 03-10. Only the changes are referenced here. The other content remains the same.:

explain the significance of {glossary_url}cross-cutting-concerns[cross-cutting concerns], , for example persistence, communication, GUI, error handling, concurrency, energy efficiency
...
design cross-cutting concepts that provide the solution approach for the corresponding cross-cutting concerns