Adjust property names for package dependencies to original proposal

[jsoriano]

What does this PR do?

When declaring package dependencies, use "package" in all cases for the package name, so all declarations are consistent. This is also coherent with the original proposal.

Also, add "source" in test dependencies, as a way to indicate the source of the package to install or reuse, instead of retrieving it form the package registry. This is useful for development of packages that live in the same repository.

Thanks @teresaromero for reporting!

Why is it important?

For consistency and coherence with the original proposal.

Checklist

• I have added test packages to test/packages that prove my change is effective.
• I have added an entry in spec/changelog.yml. No need as this modifies a feature not released yet.

Related issues

• Related to [Change Proposal] Add support for dependencies in integration packages #1083.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e0b0460 and f94d5eb.

📒 Files selected for processing (3)

• code/go/internal/validator/semantic/validate_test_package_requirements.go
• code/go/internal/validator/semantic/validate_test_package_requirements_test.go
• spec/integration/data_stream/_dev/test/config.spec.yml

---

📝 Walkthrough

Walkthrough

Parsing of manifest requirements was changed from the name field to package across semantic validators and tests. Validators now read package (and version when present), added a helper to validate source paths, and broadened data-stream test-config patterns. Integration test schema was updated to allow either a package+version object or a source object (oneOf). Test fixtures, manifests, and specs were updated and new test files for source-based requirements were added.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@code/go/internal/validator/semantic/validate_test_package_requirements.go`:
- Around line 245-251: In validateTestRequirementSource, reject absolute source
paths instead of relying on filepath.Join (which skips the config dir for
absolute inputs); add an explicit check using filepath.IsAbs(source) and return
a specerrors.NewStructuredErrorf indicating the source must be a relative path
before computing targetPath and calling os.Stat. Ensure you reference
validateTestRequirementSource and use filepath.IsAbs(source) to guard against
absolute paths.

---

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2444365 and e0b0460.

📒 Files selected for processing (3)

• code/go/internal/validator/semantic/validate_test_package_requirements.go
• code/go/internal/validator/semantic/validate_test_package_requirements_test.go
• test/packages/good_requires/_dev/test/config.yml

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: e0b0460

History

• 💚 Build #1907 succeeded 2444365

cc @jsoriano

had some thoughts after approval, left couple comments