fix(dropdown): target overloads - toggle interop method, return types

[damyanpetev]

Description

Closes #296, which is ported from old internal boards.
Found in #286, fixed separately here
Fix dropdown toggle overload call and return type of all target overloads, unit test setup & coverage

Type of Change (check all that apply):

• Bug fix
• New functionality
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactoring (no functional changes)
• Documentation
• Demos
• CI/CD
• Tests
• Changelog

Component(s) / Area(s) Affected:

How Has This Been Tested?

• Unit tests
• Manual testing
• Automated e2e tests

Test Configuration:

• .NET version:
• Hosting model:
• Browser(s):
• OS:

Screenshots / Recordings

Checklist:

• All relevant tags have been applied to this PR
• This PR includes unit tests covering all the new code
• This PR includes API docs for newly added methods/properties
• This PR includes general feature table updates in the root README.MD
• This PR includes CHANGELOG.MD updates for newly added functionality
• This PR contains breaking changes
• This PR includes behavioral changes and the feature specification has been updated with them
• Accessibility (ARIA, keyboard navigation, focus management) has been verified

Closes #

[Copilot]

Pull request overview

This PR fixes the IgbDropdown “target” overloads so they call the correct JS method (toggle instead of show) and align their return semantics with the rest of the show/hide/toggle API, while extending the interop contract test harness to validate element-handle marshalling and adding unit coverage for the corrected overloads.

Changes:

• Fix IgbDropdown.Toggle(Object) to invoke "toggle" and update target overloads to return bool/Task<bool> with proper return decoding.
• Extend the interop test harness/contract model to capture and assert ElementReference handle payloads and render-sourced expected values.
• Add DropdownTests coverage for show/toggle target overloads for both component and ElementReference anchors.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
tests/IgniteUI.Blazor.Tests/Interop/RendererMessageInteropHarness.cs	Captures marshalled ElementReference[] payloads from igSendMessage invocations.
tests/IgniteUI.Blazor.Tests/Interop/InteropHarness.cs	Extends InteropMethodCall with element-handle payloads.
tests/IgniteUI.Blazor.Tests/Interop/ComponentContract.cs	Adds render-sourced expectations (FromRender) and expected element-handle assertions to method specs.
tests/IgniteUI.Blazor.Tests/DropdownTests.cs	Adds contract-based tests for show/toggle target overloads using component and ElementReference anchors.
tests/IgniteUI.Blazor.Tests/ComponentWithContractTestBase.cs	Resolves render-sourced expected args and asserts carried element handles in recorded invocations.
src/componentsBase/WebInputs/Dropdown.cs	Fixes toggle target overload dispatch and aligns return types/decoding for show/toggle target overloads.
skills/igniteui-blazor-lite-testing/references/interop-contracts.md	Documents new interop-contract authoring patterns for render-sourced args and element handles.

[MayaKirova]

These are also some of the suppressed methods in bulk automation due to bugs: https://github.com/IgniteUI/igniteui-blazor/blob/master/tests/IgniteUI.Blazor.Lite.TestBed/componentsConfig.json#L121
These can be removed from the config now.