Use strong typing for blazor components

[rajsite]

😯 Problem to Solve

The blazor component wrappers leverage the CaptureUnmatchedValues feature to allow users to set arbitrary html attributes that are forwarded to the nimble component. For example:

<NimbleBreadcrumbItem class="my-class">Page 1</NimbleBreadcrumbItem>

However, this is untyped, lets users set arbitrary attributes, and lets users accidentally use untyped attributes instead of typed equivalents, ie:

<NimbleBreadcrumbItem href="#">Page 1</NimbleBreadcrumbItem>

instead of:

<NimbleBreadcrumbItem Href="#">Page 1</NimbleBreadcrumbItem>

Having loose typing makes it easier to accidentally break applications when refactoring / upgrading nimble.

In addition Microsoft warns about performance issues using CaptureUnmatchedValues.

A trade-off that may need to be documented is that users will not be able to leverage arbitrary data-* attributes in the strict template approach. See original discussion https://github.com/ni/nimble/pull/738#discussion_r971347578

💁 Proposed Solution

1. Remove usage of CaptureUnmatchedValues from our blazor components
2. Create a base class for the common shared attributes we want to enable like Class, Id, Slot, Name, etc

📋 Tasks

[rajsite]

Some additional discussion points:

• Can we do a survey of existing AdditionalProperties added to NimbleComponents in client applications. We know some such as id and class but are there additional ones that are used we should make sure to capture.
• Can we do something to avoid breaking applications, such as use the property name class instead of Class to prevent a breaking change in applications? Is that worth the inconsistency with other property names? From discussion: https://github.com/ni/nimble/pull/1141#discussion_r1154697846