feat(Tab): update chrome tab style

[ArgoZhang]

Link issues

fixes #5748

Summary By Copilot

Regression?

• Yes
• No

Risk

• High
• Medium
• Low

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

☑️ Self Check before Merge

⚠️ Please check all items below before review. ⚠️

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• Merge the latest code from the main branch

Summary by Sourcery

Update Chrome tab styling with visual enhancements and minor code improvements

New Features:

• Add visual separator between inactive tabs using a subtle vertical line

Bug Fixes:

• Remove unnecessary [NotNull] attributes in Layout component

Enhancements:

• Improve tab styling with hover and inactive state visual treatments
• Simplify code in Layout component with collection initialization syntax

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the style of Chrome tabs by adding a vertical divider between inactive tabs and refines the Layout component by adjusting nullable annotations and updating the AdditionalAssemblies initialization.

Updated class diagram for the Layout component

classDiagram
  class Layout {
    IEnumerable~Assembly~? AdditionalAssemblies
    string? TooltipText
  }

Loading

File-Level Changes

Change	Details	Files
Updated the style of the Chrome tabs to include a vertical divider between inactive tabs and removed content on hover.	Added a vertical divider between inactive tabs using a pseudo-element. Removed the divider on hover for a cleaner look. Adjusted styles for inactive tabs to hide the divider when hovering over adjacent tab items.	src/BootstrapBlazor/Components/Tab/Tab.razor.scss
Made nullable annotation changes to properties in the Layout component and updated the AdditionalAssemblies initialization.	Changed AdditionalAssemblies and TooltipText properties to nullable. Updated the initialization of AdditionalAssemblies to use a list literal instead of an array.	src/BootstrapBlazor/Components/Layout/Layout.razor.cs

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#5748	Update the style of Chrome tabs.	✅

Possibly linked issues

• feat(Tab): update chrome tab style #5748: The PR updates the chrome tab style to include a separator between tabs.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @ArgoZhang - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider if the added CSS rules should be behind a CSS isolation scope.
• Check if AdditionalAssemblies can be nullable, and if so, consider using the null-conditional operator to avoid the need for the null check.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (34f1e9b) to head (265fa4d).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #5749   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          657       657           
  Lines        29923     29923           
  Branches      4245      4245           
=========================================
  Hits         29923     29923           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.