Avoid "Cannot add name" error for ParamArray and Optional arguments

[DecimalTurn]

This pull request adds vbaListener.test.ts with 2 tests to ensure that no LSP related errors occur during parsing of ParamArray and Optional argument statements. The fix is also included: ensuring that we push a name to the context via this.pushNameElement(ctx);.

[Copilot]

Pull request overview

This PR prevents the “Cannot add name …” LSP error during parsing of Optional parameters and ParamArray arguments by ensuring the listener always pushes an active NameExpressionElement context before recording parameter identifiers, and adds integration tests to guard against regressions.

Changes:

• Push a NameExpressionElement for OptionalParam and ParamArray contexts before adding identifier contexts.
• Extend NameExpressionContext to include OptionalParamContext and ParamArrayContext.
• Add Mocha integration tests that parse representative VBA snippets and assert no error-level LSP logs are emitted.

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
server/src/test/vbaListener.test.ts	Adds integration tests that parse VBA code containing Optional and ParamArray parameters and assert no error logs are emitted.
server/src/project/parser/vbaListener.ts	Fixes missing name-element push for enterOptionalParam and enterParamArray, preventing “Cannot add name” errors.
server/src/project/elements/naming.ts	Broadens NameExpressionContext union to allow using OptionalParamContext/ParamArrayContext as NameExpressionElement containers.
package.json	Adds dedent for tests and formats activationEvents as a multi-line array.
package-lock.json	Locks the newly added dedent dev dependency.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.