[release/v7.5] Remove the old fuzzy suggestion and fix the local script file name suggestion

[pwshBot]

Backport of #25177 to release/v7.5

Triggered by @TravisEz13 on behalf of @daxian-dbw

Original CL Label: CL-General

/cc @PowerShell/powershell-maintainers

Impact

Choose either tooling or Customer impact.

Tooling Impact

• Required tooling change
• Optional tooling change (include reasoning)

Customer Impact

• Customer reported
• Found internally

It was a regression in 7.4, but the "FuzzyCommand" was under an experimental feature in 7.4, so users won't notice it's broken unless they turn on the feature.
However, in 7.5, the "FuzzyCommand" feature was made stable, so users start to see this issue.

Regression

• Yes
• No

stopped working in 7.5

Testing

We don't think this is testable

Manually tested

Risk

• High
• Medium
• Low

[High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.]

[daxian-dbw]

We received report for this issue in Stack Overflow and Steven also received the report from other channels.

It was a regression in 7.4, but the "FuzzyCommand" was under an experimental feature in 7.4, so users won't notice it's broken unless they turn on the feature.
However, in 7.5, the "FuzzyCommand" feature was made stable, so users start to see this issue.

[TravisEz13]

/azp run PowerShell-CI-linux-packaging, PowerShell-Windows-Packaging-CI

[azure-pipelines]

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

[BrightYang906]

將 #25177 反向移植到 release/v7.5

由代表觸發@daxian-dbw

原始 CL 標籤：CL-General

/cc @PowerShell/powershell-maintainers

  影響

選擇工具或客戶影響。

Tooling Impact

• 所需工具更換
• 可選工具變更（包括理由）

Customer Impact

•   客戶報告
•   內部發現

這是 7.4 中的回歸，但「FuzzyCommand」在 7.4 中屬於實驗功能，因此使用者除非開啟該功能，否則不會注意到它已損壞。然而，在 7.5 中，「FuzzyCommand」功能已經穩定，因此使用者開始看到這個問題。

  回歸

•   是的
•   不

在 7.5 中停止工作

  測試

我們認為這是不可測試的

  手動測試

  風險

•   高的
•   中等的
•   低的

[高/中/低。請說明如何衡量和應對風險，以證明該指示的合理性。 ]