update docs for env vars (#1987)

This updates docs for #1949
I feel like we shouldn't explicitly talk about lazy loading env vars,
it's just extra information for a programming language user. It should
just work out of the box.

<!-- ELLIPSIS_HIDDEN -->


----

> [!IMPORTANT]
> Update documentation for environment variables, including deprecation
warnings and new examples for Python, TypeScript, and Ruby.
> 
>   - **Documentation Updates**:
> - Removed redundant section "Setting Environment Variables" from
`env-vars.mdx`.
> - Added deprecation warning for `reset_baml_env_vars` in `config.mdx`.
> - Updated `with_options.mdx` to include `env` parameter in examples
for Python, TypeScript, and Ruby.
> - Updated `setting-env-vars.mdx` to remove outdated examples and
clarify usage of `dotenv` in Python, TypeScript, and Ruby.
>   - **Behavior**:
> - Environment variables are now lazily loaded on each function call,
as noted in `config.mdx`.
> 
> <sup>This description was created by </sup>[<img alt="Ellipsis"
src="https://img.shields.io/badge/Ellipsis-blue?color=175173">](https://www.ellipsis.dev?ref=BoundaryML%2Fbaml&utm_source=github&utm_medium=referral)<sup>
for 1ddf894. You can
[customize](https://app.ellipsis.dev/BoundaryML/settings/summaries) this
summary. It will automatically update as commits are pushed.</sup>


<!-- ELLIPSIS_HIDDEN -->

---------

Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>

Author: ba11b0y

fern/03-reference/baml/env-vars.mdx

@@ -21,7 +21,6 @@ client<llm> MyCustomClient {
 }
 ```
 
-## Setting Environment Variables
 <Markdown src="/snippets/setting-env-vars.mdx" />
 
 ## Error Handling

fern/03-reference/baml_client/config.mdx

@@ -29,26 +29,11 @@ python my_program_using_baml.py
 
 <Tabs>
   <Tab title="python">
-    > **Warning**: If you are using the `python-dotenv` package, please check the import order for some edge cases.
-
-    ```python
-    import dotenv
-    from baml_client import b
-    # This will work regardless of import order, since dotenv is imported as a module
-    dotenv.load_dotenv()
-    ```
-
-    ```python
-    from baml_client import b
-    from dotenv import load_dotenv
-    # This will work since load_dotenv is imported after baml_client
-    load_dotenv()
-    ```
 
     ```python
     from dotenv import load_dotenv
     from baml_client import b
-    # This will not work as expected since baml_client is imported AFTER load_dotenv
+
     load_dotenv()
     ```
   </Tab>
@@ -58,52 +43,13 @@ python my_program_using_baml.py
     import dotenv from 'dotenv'
     import { b } from './baml_client'
 
-    // This should "just work"!
     dotenv.config()
     ```
   </Tab>
   <Tab title="ruby">
     ```ruby
     require 'dotenv/load'
-
-    # Wait to import the BAML client until after loading environment variables
-    # reset_baml_env_vars is not yet implemented in the Ruby client
     require 'baml_client'
     ```
   </Tab>
 </Tabs>
-
-
-### For Your App (Manually)
-
-<Info>
-Requires BAML Version 0.57+
-</Info>
-
-Reset the environment variables to those manually set in your code.
-
-<Tabs>
-  <Tab title="python">
-    ```python
-    from baml_client import b
-    from baml_client.config import reset_baml_env_vars
-
-    # This will load the environment variables from the .env file
-    reset_baml_env_vars({ "OPENAI_API_KEY": "sk-super-secret-key" })
-    ```
-  </Tab>
-  <Tab title="typescript">
-    ```typescript
-    // Wait to import the BAML client until after loading environment variables
-    import { b } from './baml_client'
-    import { resetBamlEnvVars } from './baml_client/config'
-
-    resetBamlEnvVars({ "OPENAI_API_KEY": "sk-super-secret-key" })
-    ```
-  </Tab>
-  <Tab title="ruby">
-    ```ruby
-    # not implemented yet
-    ```
-  </Tab>
-</Tabs>