UVL Feature Requests from MODEVAR'24b

[h3ssto]

As discussed at MODEVAR'24b:

Goal: Express KConfig variability with UVL

• [ ] Add a language level for tri-state features or describe a mechanism to encode those with other language levels
• [ ] What is needed otherwise to encode KConfig / CDL / pure::*?
  • Dependend import of submodules?

Goal: Add temporal context to UVL, discussed

• Encode changes to a feature via deltas as attributes? Example: FeatureA was renamed to "Feature A" after the commit f13ee4, e.g.:

  features
  "Feature A" {name:f13ee4 = "FeatureA"}