Project priming disabling option added to lsp server

[nozjkoitop]

Make auto priming optional

java.lsp.server automatically attempts project priming during project open by invoking ActionProvider.COMMAND_PRIME when the action is available and enabled.
Priming is useful by default, but currently there is no server-level switch to suppress it for environments where automatic background build activity is undesirable (resource-constrained, offline, policy-restricted, or deterministic startup scenarios)

This behavior has caused user-facing issues (f.e. oracle/javavscode#490)

This change introduces an explicit disableProjectPriming flag for automatic project priming in Server.primeProjects(...)

Key points:

• Default behavior unchanged (priming still on by default)
• Project-open bookkeeping/synchronization remains unchanged
• Low risk, narrow scope

PR approval and merge checklist:

1. Was this PR correctly labeled, did the right tests run? When did they run?
2. Is this PR squashed?
3. Are author name / email address correct? Are co-authors correctly listed? Do the commit messages need updates?
4. Does the PR title and description still fit after the Nth iteration? Is the description sufficient to appear in the release notes?

If this PR targets the delivery branch: don't merge. (full wiki article)