docs: add inline SBDL declarations to Gherkin feature files

[Copilot]

Embeds SBDL declarations directly in the Gherkin .feature files instead of deriving them via Python conversion scripts, keeping definitions close to the source they describe.

Changes

• Added # @sbdl inline comments directly below each Feature:, Rule:, and Scenario: keyword line in all 6 feature files under test/cpp/features/
• Uses test-specification mapping as the canonical inline form:
  • Features → aspect (slug identifier, e.g. compatibility)
  • Rules → requirement (REQ ID slug, e.g. req-comp-0001) with aspect is <feature-slug>
  • Scenarios → test with requirement is <req-slug>
• No custom:title — identifiers are short meaningful slugs; the Gherkin element name is the human-readable title

Feature: Compatibility
  # @sbdl compatibility is aspect { description is "As a software craftsperson, I want my development environment to be compatible with commonly used tools and systems." }

  @REQ-COMPAT-0001
  Rule: Open Container Initiative (OCI) Image Specification
    # @sbdl req-compat-0001 is requirement { description is "amp-devcontainer images *SHALL* be compatible with the [OCI image specification](...)" aspect is compatibility }

Running sbdl test/cpp/features/*.feature now extracts all 31 SBDL elements (6 aspects, 23 requirements, 2 tests) directly from the annotated feature files.

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Pull Request Report (#1172)

Static measures

Description	Value
Number of added lines	31
Number of deleted lines	0
Number of changed files	6
Number of commits	2
Number of reviews	0
Number of comments (w/o review comments)	1
Number of reviews that contains a comment to resolve	0
Number of reviews that requested a change from the author	0
Number of reviews that approved the Pull Request	0
Get the total number of participants of a Pull Request	3

Time related measures

Description	Value
PR lead time (from creation to close of PR)	21.5 Hours
Time that was spend on the branch before the PR was created	1 Sec
Time that was spend on the branch before the PR was merged	0 Sec
Time to merge after last review	0 Sec

Status check related measures

Description	Value
Total runtime for last status check run (Workflow for PR)	27 Sec
Total time spend in last status check run on PR	29 Sec