Expand AxoCmmtAs Blazor view with full drive task surface

[PTKu]

Summary

• Wraps CommandsOperateContent / CommandsMonitorContent of AxoCmmtAsView in mirrored <Tab>+<TabPage> (12 tabs): PowerAndSafety, Home, SetPosition, Override, MoveAbsolute, MoveRelative, MoveAdditive, Velocity, TorqueControl, ParameterAccess, DigitalIO, ExplicitReads.
• Wires previously-unrendered inherited AxoDrive tasks: AxoReset_Task, RestoreTask, AxoWrite/ReadParameter (int / real / bool), AxoWrite/ReadDigitalOutput, AxoReadDigitalInput, AxoReadActualPosition/Velocity/Torque, AxoReadStatus, AxoReadMotionState, AxoReadAxisInfo.
• Header gains State / ScalingReadState / Debug badges (honor [ComponentHeader] attributes on the twin).
• Layout rule applied: max 2 Axo*TaskCommandView per row, paired semantically (Power+Reset, Stop+Halt, Write+Read of same type, etc.).
• ConfigurePolling() now polls AxisType (fixes silent unit-resolution bug — PositionUnit / VelocityUnit accessors read .Cyclic without polling), plus State / ScalingReadState / Debug for the new badges.
• 24 new entries in Resources/Strings.resx covering the added sections, pair labels and tab titles.

Test plan

• dotnet build src/components.festo.drives/src/AXOpen.Components.Festo.Drives.blazor/AXOpen.Components.Festo.Drives.blazor.csproj passes (0 errors verified locally).
• Showcase Blazor app: open a page hosting an AxoCmmtAs; verify Header badges populate (DriveState, Position/Velocity/Torque tiles, State/ScalingReadState/Debug).
• In Operate (manual) mode, click through every tab; verify each task button triggers the matching task, inputs accept values, no two task buttons land on the same row beyond pair count.
• In Monitor mode, verify every tab mirrors Operate (same tabs, order, content) with *StatusView widgets and Display controls.
• Verify Position/Velocity unit labels in the header resolve to mm/mm/s or deg/deg/s (proves the AxisType poll fix).
• Verify all 24 new resx keys render localized strings (no [Missing: ...] placeholders).