feat(registry): validate implementation versions before registration (#337)

[Ayfataan]

Summary

• Add a runtime interface-version entrypoint to the shared upgradeable interface and implement it across all eight contracts.
• Validate the target contract reports the current interface version before storing a version mapping; unsupported or unavailable targets fail with InvalidInput.
• Reject duplicate (kind, version) registrations with AlreadyExists and non-increasing versions with InvalidInput; registry admin authorization remains required.
• Add registry tests for compatible registration, incompatible targets, duplicate versions, and downgrades, plus runtime interface-compliance coverage.

Validation

• cargo test --package astroid-registry could not run because cargo is not installed or available on PATH.
• git diff --check passed.

Closes #337

[drips-wave]

@Ayfataan Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[Cjay-Cyber-2]

CI Checks Failed — Action Needed

The continuous integration checks on this pull request are failing. I can't merge until all required checks pass.

Failing checks:

• clippy: failure
• build: failure
• fmt: failure

What to do: review the failing checks in the "Checks" tab above, fix the issues in your code, and push the changes.

[Cjay-Cyber-2]

Merge Conflict — Action Needed

This pull request has merge conflicts with the base branch (main).

What to do: update your branch by merging or rebasing against main, resolve any conflicts locally, and push the result.

[Cjay-Cyber-2]

CI Checks Failed — Action Needed

The continuous integration checks on this pull request are failing. I can't merge until all required checks pass.

Failing checks:

• clippy: failure
• build: failure
• fmt: failure

What to do: review the failing checks in the "Checks" tab above, fix the issues in your code, and push the changes.

[Cjay-Cyber-2]

Merge Conflict — Action Needed

This pull request has merge conflicts with the base branch (main).

What to do: update your branch by merging or rebasing against main, resolve any conflicts locally, and push the result.

[Cjay-Cyber-2]

CI Checks Failed — Action Needed

The continuous integration checks on this pull request are failing. I can't merge until all required checks pass.

Failing checks:

• clippy: failure
• build: failure
• fmt: failure

What to do: review the failing checks in the "Checks" tab above, fix the issues in your code, and push the changes.

[Cjay-Cyber-2]

Merge Conflict — Action Needed

This pull request has merge conflicts with the base branch (main).

What to do: update your branch by merging or rebasing against main, resolve any conflicts locally, and push the result.

[Cjay-Cyber-2]

CI Checks Failed — Action Needed

The continuous integration checks on this pull request are failing. I can't merge until all required checks pass.

Failing checks:

• clippy: failure
• build: failure
• fmt: failure

What to do: review the failing checks in the "Checks" tab above, fix the issues in your code, and push the changes.

[Cjay-Cyber-2]

Merge Conflict — Action Needed

This pull request has merge conflicts with the base branch (main).

What to do: update your branch by merging or rebasing against main, resolve any conflicts locally, and push the result.

[Cjay-Cyber-2]

Merge Conflict — Action Needed

This pull request has merge conflicts with the base branch (main).

What to do: update your branch by merging or rebasing against main, resolve any conflicts locally, and push the result.

[Cjay-Cyber-2]

CI Checks Failed — Action Needed

The continuous integration checks on this pull request are failing. I can't merge until all required checks pass.

Failing checks:

• clippy: failure
• build: failure
• fmt: failure

What to do: review the failing checks in the "Checks" tab above, fix the issues in your code, and push the changes.

[Cjay-Cyber-2]

Merge Conflict — Action Needed

This pull request has merge conflicts with the base branch (main).

What to do: update your branch by merging or rebasing against main, resolve any conflicts locally, and push the result.

[Cjay-Cyber-2]

CI Checks Failed — Action Needed

The continuous integration checks on this pull request are failing. I can't merge until all required checks pass.

Failing checks:

• clippy: failure
• build: failure
• fmt: failure

What to do: review the failing checks in the "Checks" tab above, fix the issues in your code, and push the changes.

[Cjay-Cyber-2]

Merge Conflict — Action Needed

This pull request has merge conflicts with the base branch (main).

What to do: update your branch by merging or rebasing against main, resolve any conflicts locally, and push the result.

[Cjay-Cyber-2]

CI Checks Failed — Action Needed

The continuous integration checks on this pull request are failing. I can't merge until all required checks pass.

Failing checks:

• clippy: failure
• build: failure

What to do: review the failing checks in the "Checks" tab above, fix the issues in your code, and push the changes.

[Cjay-Cyber-2]

CI Checks Failed — Action Needed

The continuous integration checks on this pull request are failing. I can't merge until all required checks pass.

Failing checks:

• build: failure
• clippy: failure

What to do: review the failing checks in the "Checks" tab above, fix the issues in your code, and push the changes.

[Cjay-Cyber-2]

CI Checks Failed — Action Needed

The continuous integration checks on this pull request are failing. I can't merge until all required checks pass.

Failing checks:

• clippy: failure
• build: failure

What to do: review the failing checks in the "Checks" tab above, fix the issues in your code, and push the changes.