Revisit Need for Conda-only support and `setup_simopt` Scripts

[Grochocinski]

Is your feature request related to a problem?

Prior to V1.2, data farming was handled via Ruby. To facilitate the process, SimOpt specifically only support Conda-based python installs in order to allow for the Ruby conda-package to be utilized instead of depending on an external Ruby version. Additionally, the setup_simopt scripts were created to automate the Conda-dependency installation process (including the necessary Ruby gems).

As of V1.2, data farming no longer depends on Ruby and thus the main reason of mandating Conda (the easy to install Ruby backend) no longer exists, and the reason for having the setup_simopt scripts (streamlining the potentially complicated Ruby + gem install process) also no longer exists.

Describe the solution you'd like

1. Efforts should be made to support other (non-Conda) methods of Python install such as the standard pip install or other package managers such as uv. Setup instructions should also be revised to include other popular install methods.
2. The need for the setup_simopt scripts should be revisited since now that they have been stripped of the Ruby install setup process, they are effectively just Conda environment creation/update scripts. Especially when combined with the aforementioned goal of supporting other Python install methods, I personally don't see a need for these scripts.

[Grochocinski]

working on improving this in the dependency_consolidation fix_workflow_instructions branch

[cenwangumass]

I discussed this last week with David and I'm currently thinking we can get rid of conda and just recommend uv as the preferred way of using simopt.

[Grochocinski]

I agree we can remove the Conda-specific instructions and replace them with something more generic. I'll work on instructions for using venv with both pure Python and uv (with uv being recommended). Anyone who has Conda installed should just be able to follow the pip instructions once they create a Conda environment.