fix: reset stale asset protocols on platform change

[frederick-wang]

Problem

Changing the selected asset platform refreshes protocols.el.choices, but the form intentionally does not clear the current protocols value in updatePlatformProtocols(). That preserves gateway-switch behavior, but it also means ProtocolSelector can keep protocol values from the previously selected platform.

One reproducible case is a Windows asset form that starts from a platform exposing rdp and then switches to a custom Windows OpenSSH platform exposing only ssh and sftp. The platform choices are updated correctly, but the selector can still carry the old rdp item and miss the new platform default such as sftp.

Root Cause

setDefaultItems() preferred existing asset protocol values whenever this.value was non-empty. getAssetDefaultItems() also returned the old item even when the new platform choices did not contain that protocol name. As a result, unsupported protocols could survive a platform change.

Fix

In asset protocol mode (settingReadonly), detect whether the current value contains protocol names that are absent from the new choices. If unsupported values are found, rebuild the selector items from the current platform defaults (required, primary, or default) instead of carrying stale values forward.

If the existing values are still compatible with the new platform choices, the selector keeps them, including custom ports, and still adds missing required/primary protocols as before. This keeps the behavior needed by the existing gateway-switch comment while fixing platform changes that actually replace the protocol set.

This also drops absent protocols in getAssetDefaultItems() and uses Array.isArray() / Set.has() to address the SonarCloud warnings on the changed lines.

Tests

Added ProtocolSelector unit coverage for:

• stale rdp + ssh values resetting to ssh + sftp after the platform choices change
• empty asset protocol values initializing from platform defaults
• compatible protocol values preserving custom ports
• missing required protocols being added to compatible values

Validated locally with:

• npm_config_registry=https://registry.npmmirror.com npx -y yarn@1.22.22 install --frozen-lockfile --registry https://registry.npmmirror.com --network-timeout 600000
• ./node_modules/.bin/eslint src/components/Form/FormFields/ProtocolSelector/index.vue tests/unit/components/ProtocolSelector.spec.js
• git diff --check
• Docker node:20-bullseye targeted test: yarn test:unit tests/unit/components/ProtocolSelector.spec.js passed with 4 tests

Note: the full local yarn test:unit suite still has unrelated existing failures in this checkout: old Jest/Babel setup requires the Babel 7 bridge package, two utils specs import files that are not present at src/utils/index.js and src/utils/validate.js, and Breadcrumb.spec.js imports Element UI which pulls untransformed lodash-es ESM. The new ProtocolSelector spec passes in the isolated Docker test environment.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[ZhaoJiSen]

@frederick-wang 您描述的这个问题 经过测试确实复现了，当平台设置了 protocol 之后后续增加或减少的时候资产并不会同步它已经配置的资产，但是当前代码经过我测试我发现当我设置为支持 4 个协议后，资产与之配置 4个协议，Plateform 减少一个，不切换 Plateform 此时资产直接变为 1 个。因此这需要更多的一个考量

[ZhaoJiSen]

@frederick-wang 如果可以请进一步补充更多的复现细节