fix(amazonq): enable agentic chat in AL2

[leigaol]

Problem

LSP depends on node 18 which depends on GLIBC >=2.28.
Amzn al2 instances do not have GLIBC >=2.28.

Solution

Use the patch of glibc if it is available.

---

• Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
• Your code changes must meet the guidelines in CONTRIBUTING.md.
• License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

[github-actions]

• This pull request modifies code in src/* but no tests were added/updated.
  • Confirm whether tests should be added or ensure the PR description explains why tests are not required.
• This pull request implements a feat or fix, so it must include a changelog entry (unless the fix is for an unreleased feature). Review the changelog guidelines.
  • Note: beta or "experiment" features that have active users should announce fixes in the changelog.
  • If this is not a feature or fix, use an appropriate type from the title guidelines. For example, telemetry-only changes should use the telemetry type.

[Hweinstock]

verified the build works for me in cloud desktop as well!

[Hweinstock]

I've verified with the latest commit, I can still execute tools and use agentic chat in my dev desktop!

Also tested this in non-dev desktop and language server starts up normally.

[jpinkney-aws]

Mine worked on my old dev desktop but on the new one it fails because /opt/vsc-sysroot/lib64/ld-linux-x86-64.so.2 isn't defined

[justinmk3]

here are the 2 places that decide the path to node+args:

aws-toolkit-vscode/packages/amazonq/src/lsp/client.ts

Lines 49 to 51 in 8b7106b

	const serverModule = resourcePaths.lsp
	const argv = [

aws-toolkit-vscode/packages/core/src/amazonq/lsp/lspClient.ts

Lines 254 to 262 in 8b7106b

	const serverModule = resourcePaths.lsp
	const serverOptions = createServerOptions({
	encryptionKey: key,
	executable: resourcePaths.node,
	serverModule,
	// TODO(jmkeyes): we always use the debug options...?
	execArgv: debugOptions.execArgv,
	})

each of those then passes nodePath (+args) to various functions.

[opieter-aws]

The linter is failing on the fs import

[leigaol]

follow up: Check if aarch64 has this issue or not.

[murkvin]

It looks like you've only configured this for x86_64. If you want this to work on aarch64, then you'll need to point to ld-linux-aarch64.so.1.

Please check out my overall comment.

[murkvin]

It seems that this PR takes a dependency on some resources that we drop onto hosts as a component of another project. This is fine, but we should connect to discuss and formalize the interface.

For example, we already vend a static, architecture-independent path to the linker as part of our public interface. Using this would make your code more robust and abstract away platform concerns.

I don't expect to move these files around on people's machines, but I'd rather that doing so didn't break this plugin on AL2.

[murkvin]

It looks like you've only configured this for x86_64. If you want this to work on aarch64, then you'll need to point to ld-linux-aarch64.so.1.

Please check out my overall comment.