Add Behavior Annex language server services

[lwrage]

Wires the Behavior Annex into the language server now that OSATE serves the annex through Xtext, and follows the consequences of that switch through the extension, the CLI, and the build.

Behavior Annex services

BehaviorAnnexLsSetup mixes the BA runtime and generic IDE modules and is registered both as an ISetup service and in Aadl2LsResourceServiceProviderRegistry, so the language-server injectors win the aadl registration rather than OSATE's Eclipse-oriented ones. BehaviorAnnexLsRuntimeModule keeps the normal BA runtime services but swaps Eclipse project scoping for the multi-root Aadl2LsGlobalScopeProvider.

EmbeddedBehaviorAnnexContentAssistService handles completion inside an embedded annex subclause. It locates the annex leaf at the request offset, confirms the enclosing DefaultAnnexSubclause parsed to a BehaviorAnnex, and either answers reference positions directly from BehaviorAnnexReferenceProposalService or replays the annex text into a synthetic BA resource and delegates. Any position that is not embedded BA text, and any failure, falls through to the normal AADL path.

OSATE pin

The branch previously pinned a local OSATE commit that never reached osate/osate2, so CI could not check the submodule out. That work is now upstream through PRs #3144–#3150, and the pin follows osate/osate2 master at 0561df2e.

It briefly sat one commit behind, at aafcbaae, because master's tip 0aa9711 ("version updates") bumped org.osate.ge.ba to 3.0.0 while org.osate.ge.ba.tests still declared Fragment-Host: org.osate.ge.ba;bundle-version="[2.2.2,3.0.0)". Tycho could not resolve the fragment, so the OSATE reactor failed before the language server was reached. Upstream 37a7f77 ("Fix dependency version") widens that range to [3.0.0,4.0.0) and adds the Eclipse project metadata the fragment was missing, so the pin now moves to the tip. The one commit after that fix, 0561df2e, only edits releng/osate.releng/OSATE2.launch, which no build reads.

Consequences of the Xtext switch

The legacy BA parser needed ANTLR 4.4, extracted from the org.osate.ba bundle into the p2 repository by an antrun step. The Xtext-generated parser links against the ANTLR 3 runtime that already ships as an OSGi bundle, so the extraction and everything downstream of it goes away:

• the antrun extraction in org.osate.aadl.ls.repository/pom.xml, and the extension's serverClasspath requirement and newer-runtime filter;
• the same requirement in the CLI workspace server's buildServerClassLoader, which otherwise threw before the embedded server started and failed all five EndToEndIT cases with server died before emitting port, logging the cause only to a workspace log the test never reads. It now requires a non-empty plug-in directory, which still catches a misresolved aadl.plugins.dir;
• the packaged-runtime check in scripts/build-test-release, which expected two org.antlr.runtime bundles plus antlr-runtime-4.4.jar. It now requires exactly one at 3.x, which still catches two versions of those classes on one classloader, and org.antlr.runtime loses its duplicate-bundle exemption.

org.osate.ba.feature joins category.xml so the annex is packaged, and InstantiateCommand adapts to OSATE 2.20 returning a typed diagnostic kind.

Build parallelism

Only the OSATE build is large enough to earn -T6. The language server, extension, and CLI reactors are small, and serial builds keep their output readable and their module ordering as declared.

Validation

./scripts/build-test-release passes from a clean state on the 0561df2e pin — all 145 OSATE modules including org.osate.ge.ba.tests — and ./scripts/assert-test-counts confirms no suite silently vanished:

ok       language server AllTests     34 executed
ok       workspace server EndToEndIT  5 executed
ok       assembled CLI CliEndToEndIT  15 executed
ok       CLI ArgParserTest            26 executed
ok       CLI VersionTest              4 executed

🤖 Generated with Claude Code