MudDataGrid, MudTable: Add TableAttributes parameter

[NoahS2003]

Added a TableAttributes parameter to the MudDataGrid and MudTable that allows for HTML attributes on the underlying table element. This adds support for accessibility features like aria-label and aria-labelledby.

Deprecated the AriaLabel parameter on MudTable, as it can be set by TableAttributes.

Checklist:

• I've read the contribution guidelines
• My code follows the style of this project
• I've added or updated relevant unit tests

[NoahS2003]

Related to #12642, but that issue seems to be specific to the SelectColumn rather than the root table element.

[danielchalmers]

Would it be better in general to use aria-labelledby for this as it should already be labeled somewhere on the screen anyway? Or add a TableAttributes property so people can use either one? This could be done in MudTable as well in addition to deprecating the AriaLabel property on there.

[NoahS2003]

@danielchalmers Will do. I think the generalized TableAttributes will add more value, so I'll do that. Is there an existing process for deprecating a parameter? I can't find it in the contributing guidelines.

[danielchalmers]

Is there an existing process for deprecating a parameter?

We typically just mark with [Obsolete] but keep it functional. Then in the next major release we remove it along with associated tests/logic.

Example:

        [Parameter]
        [Category(CategoryTypes.Table.Behavior)]
        [Obsolete("Set via TableAttributes....etc")]
        public string? AriaLabel { get; set; }

[NoahS2003]

@danielchalmers

Is there an existing process for deprecating a parameter?

We typically just mark with [Obsolete] but keep it functional. Then in the next major release we remove it along with associated tests/logic.

Example:

        [Parameter]
        [Category(CategoryTypes.Table.Behavior)]
        [Obsolete("Set via TableAttributes....etc")]
        public string? AriaLabel { get; set; }

I can't seem to keep it functional with it marked obsolete, it looks like there are some build rules that throw errors when obsolete parameters are used. Is there a way to get around that?

[danielchalmers]

Thank you!