fix: prevent users from passing on_complete in transaction params on …

…app_client calls

BREAKING CHANGE: prevent users from passing on_complete in transaction params on app_client calls

docs/html/_sources/capabilities/debugging.md.txt

@@ -1,14 +1,14 @@
 # Debugger
 
-The AlgoKit Python Utilities package provides a set of debugging tools that can be used to simulate and trace transactions on the Algorand blockchain. These tools and methods are optimized for developers who are building applications on Algorand and need to test and debug their smart contracts via [AVM Debugger extension](link to vscode extension).
+The AlgoKit Python Utilities package provides a set of debugging tools that can be used to simulate and trace transactions on the Algorand blockchain. These tools and methods are optimized for developers who are building applications on Algorand and need to test and debug their smart contracts via [AlgoKit AVM Debugger extension](https://marketplace.visualstudio.com/items?itemName=algorandfoundation.algokit-avm-vscode-debugger).
 
 ## Configuration
 
 The `config.py` file contains the `UpdatableConfig` class which manages and updates configuration settings for the AlgoKit project. The class has the following attributes:
 
 -   `debug`: Indicates whether debug mode is enabled.
--   `project_root`: The path to the project root directory. Can be ignored if you are using `algokit_utils` inside an `algokit` compliant project (containing `.algokit.toml` file). For non algokit compliant projects, simply provide the path to the folder where you want to store sourcemaps and traces to be used with [`AVM Debugger`](links to extension). Alternatively you can also set the value via the `ALGOKIT_PROJECT_ROOT` environment variable.
--   `trace_all`: Indicates whether to trace all operations. Defaults to false, this means that when debug mode is enabled, any (or all) application client calls performed via `algokit_utils` will store responses from `simulate` endpoint. These files are called traces, and can be used with [AVM Debugger](link to vscode extension) to debug TEAL source codes, transactions in the atomic group and etc.
+-   `project_root`: The path to the project root directory. Can be ignored if you are using `algokit_utils` inside an `algokit` compliant project (containing `.algokit.toml` file). For non algokit compliant projects, simply provide the path to the folder where you want to store sourcemaps and traces to be used with [`AlgoKit AVM Debugger`](https://github.com/algorandfoundation/algokit-avm-vscode-debugger). Alternatively you can also set the value via the `ALGOKIT_PROJECT_ROOT` environment variable.
+-   `trace_all`: Indicates whether to trace all operations. Defaults to false, this means that when debug mode is enabled, any (or all) application client calls performed via `algokit_utils` will store responses from `simulate` endpoint. These files are called traces, and can be used with `AlgoKit AVM Debugger` to debug TEAL source codes, transactions in the atomic group and etc.
 -   `trace_buffer_size_mb`: The size of the trace buffer in megabytes. By default uses 256 megabytes. When output folder containing debug trace files exceedes the size, oldest files are removed to optimize for storage consumption.
 -   `max_search_depth`: The maximum depth to search for a an `algokit` config file. By default it will traverse at most 10 folders searching for `.algokit.toml` file which will be used to assume algokit compliant project root path.
 

docs/html/capabilities/debugging.html

@@ -77,14 +77,14 @@
 
   <section id="debugger">
 <h1>Debugger<a class="headerlink" href="#debugger" title="Permalink to this heading"></a></h1>
-<p>The AlgoKit Python Utilities package provides a set of debugging tools that can be used to simulate and trace transactions on the Algorand blockchain. These tools and methods are optimized for developers who are building applications on Algorand and need to test and debug their smart contracts via [AVM Debugger extension](link to vscode extension).</p>
+<p>The AlgoKit Python Utilities package provides a set of debugging tools that can be used to simulate and trace transactions on the Algorand blockchain. These tools and methods are optimized for developers who are building applications on Algorand and need to test and debug their smart contracts via <a class="reference external" href="https://marketplace.visualstudio.com/items?itemName=algorandfoundation.algokit-avm-vscode-debugger">AlgoKit AVM Debugger extension</a>.</p>
 <section id="configuration">
 <h2>Configuration<a class="headerlink" href="#configuration" title="Permalink to this heading"></a></h2>
 <p>The <code class="docutils literal notranslate"><span class="pre">config.py</span></code> file contains the <code class="docutils literal notranslate"><span class="pre">UpdatableConfig</span></code> class which manages and updates configuration settings for the AlgoKit project. The class has the following attributes:</p>
 <ul class="simple">
 <li><p><code class="docutils literal notranslate"><span class="pre">debug</span></code>: Indicates whether debug mode is enabled.</p></li>
-<li><p><code class="docutils literal notranslate"><span class="pre">project_root</span></code>: The path to the project root directory. Can be ignored if you are using <code class="docutils literal notranslate"><span class="pre">algokit_utils</span></code> inside an <code class="docutils literal notranslate"><span class="pre">algokit</span></code> compliant project (containing <code class="docutils literal notranslate"><span class="pre">.algokit.toml</span></code> file). For non algokit compliant projects, simply provide the path to the folder where you want to store sourcemaps and traces to be used with [<code class="docutils literal notranslate"><span class="pre">AVM</span> <span class="pre">Debugger</span></code>](links to extension). Alternatively you can also set the value via the <code class="docutils literal notranslate"><span class="pre">ALGOKIT_PROJECT_ROOT</span></code> environment variable.</p></li>
-<li><p><code class="docutils literal notranslate"><span class="pre">trace_all</span></code>: Indicates whether to trace all operations. Defaults to false, this means that when debug mode is enabled, any (or all) application client calls performed via <code class="docutils literal notranslate"><span class="pre">algokit_utils</span></code> will store responses from <code class="docutils literal notranslate"><span class="pre">simulate</span></code> endpoint. These files are called traces, and can be used with [AVM Debugger](link to vscode extension) to debug TEAL source codes, transactions in the atomic group and etc.</p></li>
+<li><p><code class="docutils literal notranslate"><span class="pre">project_root</span></code>: The path to the project root directory. Can be ignored if you are using <code class="docutils literal notranslate"><span class="pre">algokit_utils</span></code> inside an <code class="docutils literal notranslate"><span class="pre">algokit</span></code> compliant project (containing <code class="docutils literal notranslate"><span class="pre">.algokit.toml</span></code> file). For non algokit compliant projects, simply provide the path to the folder where you want to store sourcemaps and traces to be used with <a class="reference external" href="https://github.com/algorandfoundation/algokit-avm-vscode-debugger"><code class="docutils literal notranslate"><span class="pre">AlgoKit</span> <span class="pre">AVM</span> <span class="pre">Debugger</span></code></a>. Alternatively you can also set the value via the <code class="docutils literal notranslate"><span class="pre">ALGOKIT_PROJECT_ROOT</span></code> environment variable.</p></li>
+<li><p><code class="docutils literal notranslate"><span class="pre">trace_all</span></code>: Indicates whether to trace all operations. Defaults to false, this means that when debug mode is enabled, any (or all) application client calls performed via <code class="docutils literal notranslate"><span class="pre">algokit_utils</span></code> will store responses from <code class="docutils literal notranslate"><span class="pre">simulate</span></code> endpoint. These files are called traces, and can be used with <code class="docutils literal notranslate"><span class="pre">AlgoKit</span> <span class="pre">AVM</span> <span class="pre">Debugger</span></code> to debug TEAL source codes, transactions in the atomic group and etc.</p></li>
 <li><p><code class="docutils literal notranslate"><span class="pre">trace_buffer_size_mb</span></code>: The size of the trace buffer in megabytes. By default uses 256 megabytes. When output folder containing debug trace files exceedes the size, oldest files are removed to optimize for storage consumption.</p></li>
 <li><p><code class="docutils literal notranslate"><span class="pre">max_search_depth</span></code>: The maximum depth to search for a an <code class="docutils literal notranslate"><span class="pre">algokit</span></code> config file. By default it will traverse at most 10 folders searching for <code class="docutils literal notranslate"><span class="pre">.algokit.toml</span></code> file which will be used to assume algokit compliant project root path.</p></li>
 </ul>