Fix BrickController - restoring MouldKing DI interface registration

[Copilot]

The BrickController Core Build job was failing in VendorBuilderTests because MouldKing devices had been switched to IMouldKingDeviceManager, but the Autofac registrations used by the tests did not expose that interface. This aligns the MouldKing constructor/registration path so the production container and test container resolve the same graph.

• MouldKing DI contract

  • add IMouldKingDeviceManager with the GetAppId() contract used by MouldKing devices
  • implement the interface on MouldKingDeviceManager

• Constructor dependency alignment

  • update MK3_8, MK4, MK5, MK6
  • update MKBaseByte and MKBaseNibble
  • all now depend on IMouldKingDeviceManager instead of the concrete manager type

• Autofac registration fix

  • register MouldKingDeviceManager as IMouldKingDeviceManager in MouldKing vendor registration
  • mirror the same interface registration in VendorBuilderTests so the test container matches runtime DI behavior

• Result

  • resolves the Autofac DependencyResolutionException seen in the core build job for MouldKing device resolution

builder.RegisterDeviceManager<MouldKingDeviceManager>()
    .As<IMouldKingDeviceManager>()
    .SingleInstance();