[BUG] Conflicting Executable Path Between Local and Environment Installations in Jaclang

[AshishMahendra]

Describe the bug
After installing Jaclang version 0.5.8 locally via a repository pull and using pip install ., Jac functions as expected. However, when a new Conda environment is created and Jaclang is installed through pip install jac, it defaults to installing the latest version (e.g., 0.5.11). Despite this newer version installation in the Conda environment, any operation involving the Jac executable still references the local installation version (0.5.8), leading to compatibility issues.

To Reproduce
Steps to reproduce the behavior:

1. Clone the Jaclang repository.
2. Inside the repository directory, run pip install . to install the Jaclang version locally say 0.5.8.
3. Create a new Conda environment using conda create --name test_env python=3.12.
4. Activate the new environment with conda activate test_env.
5. Install Jaclang in the new environment using pip install jac, which installs a version of, say for e.g 0.5.11.
6. Within the environment, attempt to run a Jac script using jac run test.jac. Despite being in the environment where Jaclang 0.5.11 should be used, the script execution unexpectedly utilizes the local Jaclang version 0.5.8.

Expected behavior
After installing Jaclang in a new Conda environment, all references to the Jac executable should point to the installed version (e.g., 0.5.11), not the locally installed version (0.5.8).

Jaclang/Python Version
Python version and Jac version, or installed from source.

• Local Jaclang version: 0.5.8
• Conda environment Python version: 3.12
• Jaclang version in Conda environment: 0.5.11