Fix LSP issues post core-std merger

The core and std library merger (#6729) has introduced a few failing tests that seem to be bugs within the lsp itself.
```
Failing tests:
sway-lsp::lib completion
sway-lsp::lib publish_diagnostics_dead_code_warning
sway-lsp lsp_syncs_with_workspace_edits

Failed projects:
- Project: match_expressions_or
Path: /home/runner/actions-runner/_work/sway/sway/test/src/e2e_vm_tests/test_programs/should_pass/language/match_expressions_or/src/main.sw
Error: Exit code: exit status: 1
- Project: match_expressions_unreachable_or
Path: /home/runner/actions-runner/_work/sway/sway/test/src/e2e_vm_tests/test_programs/should_pass/language/match_expressions_unreachable_or/src/main.sw
Error: Exit code: exit status: 1
- Project: fix_opcode_bug
Path: /home/runner/actions-runner/_work/sway/sway/test/src/e2e_vm_tests/test_programs/should_pass/language/fix_opcode_bug/src/main.sw
Error: Exit code: signal: 9 (SIGKILL)

```

Start by reproducing the three failing tests: sway-lsp::lib completion, sway-lsp::lib publish_diagnostics_dead_code_warning, and sway-lsp lsp_syncs_with_workspace_edits. Review the core and std library merger in #6729 alongside the listed match_expressions_or, match_expressions_unreachable_or, and fix_opcode_bug failures. Done means the LSP tests and failed projects pass without the reported exit failures.

Written by the indexing model from the issue text.