[Linux/Mac] Can't get the intellisense for @using on Blazor App

[LuckyKang79]

Environment data

dotnet --info output:

.NET SDK (reflecting any global.json):
 Version:   6.0.414
 Commit:    bf51579d4c

Runtime Environment:
 OS Name:     debian
 OS Version:  11
 OS Platform: Linux
 RID:         debian.11-x64
 Base Path:   /usr/share/dotnet/sdk/6.0.414/

global.json file:
  Not found

Host:
  Version:      6.0.22
  Architecture: x64
  Commit:       ad40cc35b5

.NET SDKs installed:
  6.0.414 [/usr/share/dotnet/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 6.0.22 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.22 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

Download .NET:
  https://aka.ms/dotnet-download

Learn about .NET Runtimes and SDKs:
  https://aka.ms/dotnet/runtimes-sdk-info

VS Code version:1.81.1
C# Extension version: v2.0.376

OmniSharp log

Steps to reproduce

1. Create a BlazorClient project and name it "BlazorClient":

dotnet new blazorwasm -ho -o BlazorClient 

2. Open Project by vscode

cd ./BlazorClient
code .

3. After C# reloads the project, the IDE requests that assets (launch.json and task.json) should be added to build and debug the project. Select Yes. And then choose BlazorClient.Server as the startup item.
   
4. Back to Terminal Emulator and create a Razor ClassLibrary by running:
   dotnet new razorclasslib --support-pages-and-views false -o RazorLib1
5. Add reference from Client app to class library
   dotnet add Client reference RazorLib1
6. Open _Imports.razor file under the Client app add a using statement for the namespace of the Razor class library
   @using RazorLib1

Note:

1.This issue also repro on lower versions of C# v2.0.357
2. This issue does not reproduce on lower versions of C# v1.26.0
3. This issue repro on Blazor Server/WASM App
4. This issue also repro on Mac OS

Expected behavior

Can get the intellisense for @using on Blazor App

Actual behavior

Can't get the intellisense for @using on Blazor App

Additional context

Add any other context about the problem here.

[LuckyKang79]

This issue is also reproduced on latest version 8.0.100-rc.2.23461.1 SDK + C# Dev Kit v0.4.10 preview (C# v2.1.2)

VS Code version: 1.82.0
C# Extension version: v2.1.2