feat(extensibility): added isActiveFilter in UMS

[yashmeet29]

Description

Change the isActive filter in the UMS transport layer to require extensions to be explicitly active before they are included in the agent's capability set.

Only extensions with isActive: true in UMS are returned by get_extension_capability_implementation(). Extensions with isActive: false or without the field are excluded.

Updated all affected unit test fixtures and inline test nodes accordingly.

Related Issue

Closes #<issue_number>

(Link to the GitHub issue this PR addresses)

Type of Change

Please check the relevant option:

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Code refactoring
• Dependency update

How to Test

End-to-end via agent behavior

Prerequisites: an agent configured with UmsTransport, connected to a UMS instance with at least one extension.

Active extension is visible — Ensure the extension is activated (isActive: true in UMS). Start the agent and interact with it using a task that would invoke one of the extension's tools. Verify the tool is executed successfully and the extension contributes to the agent's response.

Deactivated extension is hidden — Deactivate the extension via the deactivate API. Repeat the same task. Verify the agent no longer uses the extension's tools and responds as if the extension does not exist.

Legacy extension without isActive is hidden (breaking change) — If a UMS record exists without the isActive field (published before activate/deactivate was introduced), the agent should behave as if that extension is not registered. Re-deploying or activating the extension will restore its visibility.

Re-activation restores visibility — Activate the extension again. Restart or allow the agent's UMS cache to expire, then repeat the task. Verify the extension's tools are available to the agent again.

Checklist

Before submitting your PR, please review and check the following:

• I have read the Contributing Guidelines
• I have verified that my changes solve the issue
• I have added/updated automated tests to cover my changes
• All tests pass locally
• I have verified that my code follows the Code Guidelines
• I have updated documentation (if applicable)
• I have added type hints for all public APIs
• My code does not contain sensitive information (credentials, tokens, etc.)
• I have followed Conventional Commits for commit messages

Breaking Changes

Additional Notes