prep for release 0.3.0

[desmonddak]

Description & Motivation

Prepare ROHD-HCL v0.3.0 for release and publish the accumulated component, protocol, configuration-application, and compatibility improvements since v0.2.1.

A significant change is that this is now a pub workspace (a single file opens up VSCode to managing all).

Highlights include:

• Expanded AMBA support with AXI4-Lite, AXI4-Stream, ACE, and ACE-Lite variants.
• Added AsyncFifo, APB CSR completers, ready/valid infrastructure, and CAM capabilities.
• Extended CSR support with heterogeneous block sizes, configurable asynchronous reset, write-only fields, and corrected write-ones-clear behavior.
• Added optional early termination to Serializer and Deserializer, Counter.upDown, and direct register-file initialization support.
• Modernized Confapp with native ROHD schematic rendering, source and generated-code views, syntax highlighting, split-pane output, downloadable artifacts, and light/dark themes.
• Fixed AXI4 multi-beat writes and response-delay handling, non-aligned memory loading, CSR address decoding, and FifoChecker simulation failures.
• Updated compatibility to ROHD 0.6.11 and Dart 3.6.0.

The release includes several intentional breaking changes:

• The minimum supported Dart SDK is now 3.6.0.
• Affected AXI5 signals now use their protocol-correct widths.
• ChoiceConfigKnob<Type> choices now require stable choiceLabels so display and serialized values remain reliable in minified builds.

This PR finalizes the release metadata by:

• Setting the root package version to 0.3.0.
• Updating Confapp's rohd_hcl dependency to ^0.3.0.

See CHANGELOG.md for the complete release notes and migration guidance.

Related Issue(s)

Testing

All existing tests pass. We have new browser-based testing of confapp.

Backwards-compatibility

Is this a breaking change that will not be backwards-compatible? If yes, how so?

Yes. Applications must use Dart 3.6.0 or newer. Designs using the corrected AXI5 signals may need to update connected port widths, and custom configurators using ChoiceConfigKnob<Type> must provide stable labels. Migration details are included in CHANGELOG.md.

Documentation

Does the change require any updates to documentation? If so, where? Are they included?

Yes. Documentation is added in doc/ area, especially with regard to developer support.

[mkorbel1]

Looks great!