Merge branch 'Workbench-5.6' into 'master'

Copyright (c) 2017-2023, UT-Battelle, LLC

Copyright (c) 2017-2026, UT-Battelle, LLC

All rights reserved

[NEAMS Workbench]

## Whats in the bundle:

    Workbench-5.5.1.{tar.gz,dmg,exe}: NEAMS Workbench release with integrated ParaView 5.6 visualization toolkit

    Workbench-5.6.0.{tar.gz,dmg,exe}: NEAMS Workbench release with integrated ParaView 5.13 visualization toolkit

## Install NEAMS Workbench

Start the NEAMS Workbench.

    Workbench-5.5.1/bin/Workbench                 Workbench-5.5.1.tar.gz (Linux)

    Workbench-5.5.1.app/Contents/MacOS/Workbench  Workbench-5.5.1.dmg    (MacOS)

    Workbench-5.5.1\bin\Workbench.exe             Workbench-5.5.1.exe    (Windows)

    Workbench-5.6.0/bin/Workbench                 Workbench-5.6.0.tar.gz (Linux)

    Workbench-5.6.0.app/Contents/MacOS/Workbench  Workbench-5.6.0.dmg    (MacOS)

    Workbench-5.6.0\bin\Workbench.exe             Workbench-5.6.0.exe    (Windows)

>Note: The first time a version of Workbench is started on your machine an install-specific environment is setup.

      This can take a few minutes, so please be patient. A message stating `Testing for python using ...` will be presented in the terminal from which Workbench has been launched.

## NEAMS Workbench 5.6.0

### Added:

- Support for language Server protocol workspace change watching

- Support for multi-tab stop autocompletion snippets

- Support for language server data plotting extension

- Python utility script for converting WASP schema files to Python objects in support of Python-based language server integration 

- Support for SCALE2MCNP alternate SCALE run configuration

- Support for saving and loading plots from JSON-SPF format

### Changed:

- Mac bundle from Intel to ARM architecture

- ParaView 5.6 to 5.13

- PyARC v2.6.0 to v3.0.0

### Fixed:

- Mac file dialog issue by using non-native file dialog for file open and new operations

- Support for language server protocol onHover array responses

## NEAMS Workbench 5.5.1

### Added:

### Mac cannot run Workbench because the developer cannot be verified

Newer Mac operating systems require applications to be certified and signed. The Workbench team is working to support this new requirement, but in the meantime there is a workaround. After downloading and unzipping the Workbench-Darwin bundle perform the following steps:

1. Open a terminal and change directory into the root directory of the Workbench installation (E.g., /software/Workbench)

2. Remove the quarantine attribute from the Workbench executable

  - `xattr -dr com.apple.quarantine /Applications/Workbench-5.5.1.app`

3. Execute Workbench

  - `/Applications/Workbench-5.5.1.app/Contents/bin/Workbench`

1. Remove the quarantine attribute from the Workbench executable

  - `xattr -dr com.apple.quarantine /Applications/Workbench-5.6.0.app`

2. Execute Workbench

  - `/Applications/Workbench-5.6.0.app/Contents/bin/Workbench`

### Rerunning SetupRemote for MCNP after opening an MCNP input

The issue here is that the MCNP language server is running in the background due to having opened an MCNP input. During the SetupRemote process a new copy of the language server will be retrieved and installed. On Windows, because the language server is in use, the SetupRemote step fails providing an error about the file being locked. This isn't a big deal because there is currently only one language server for MCNP, but because the SetupRemote fails the new configured parameters are not properly finalized. This typically occurs when you want to change the path to MCNP on the server (E.g., because you got the path wrong the first time).