Fix RenderCV workflow failure by aligning sample CV YAML with current schema

[Copilot]

Summary

The RenderCV GitHub Actions job failed because _data/cv.yml contained top-level keys no longer accepted by the current rendercv schema. This PR removes those invalid keys so rendercv render _data/cv.yml --settings assets/rendercv/settings.yaml can pass schema validation in CI.

• Root cause
  • rendercv validation rejected unknown fields under cv: label, image, summary, address.
• Change
  • Removed unsupported top-level fields from /home/runner/work/spokiio.github.io/spokiio.github.io/_data/cv.yml.
• Result
  • Sample CV input now conforms to the schema used by the workflow job.

cv:
  name: Albert Einstein
  email: einstein@example.com
  location: Princeton, NJ
  sections:
    ...

Ownership Routing

• I confirmed this PR targets the correct repo based on docs/BOUNDARIES.md.
• This PR only changes starter-owned scope (al-folio) or I am porting a routed change and linked the owning repo issue/PR.

Owning repo (if not starter):
Related issue/PR:

Plugin Ecosystem (if applicable)

• Not applicable
• This PR proposes a plugin for featured-only listing.
• This PR proposes a plugin for bundled starter inclusion.

If plugin-related, provide:

• Plugin repo URL:
• Gem name:
• Jekyll plugin id:
• Compatibility (al_folio_min/al_folio_max):
• Demo page/post path:
• Maintainer contact:

Starter Wiring Changes

• Not applicable
• Updated Gemfile dependency wiring.
• Updated _config.yml plugin activation/config.
• Updated _data/featured_plugins.yml metadata.

Validation

• npm ci
• bundle exec jekyll build
• npm run lint:prettier
• npm run lint:style-contract
• Integration tests (test/integration_*.sh) as needed
• Visual tests (npm run test:visual) as needed

Notes

Compatibility/migration impact is limited to starter sample data: existing CV data using removed keys should be updated to match the current RenderCV schema if reused elsewhere.