[Feature] Support for proof-less execution transactions (Leo Devnode suport)

[Roee-87]

Motivation

The Leo devnode tool enables developers to rapidly iterate on their Aleo programs without having to wait for proof generation when generating execution transactions. Many developers run CI tests in JS, so having support for generating proof-less execution transactions will enable developers to use the SDK to make transactions against the devnode server.

Test Plan

Tests will require Leo devnode to be installed.

1. Install Leo using the following commit: 5baf94e
2. Initialize a Devnode server using the following command:

leo devnode start --private-key $PRIVATE_KEY --verbosity 2

This will initialize a development server at http://localhost:3030.
3. Navigate to create-leo-app/template-devnode-js.
Run yarn dev to run the example.

Related PRs

Leo devnode PR:
ProvableHQ/leo#28982

[Roee-87]

Reminder to delete before merging.

[iamalwaysuncomfortable]

This actually needs to stay here :)

[iamalwaysuncomfortable]

This is good and we should get this in, however it needs some changes.

1. We absolutely need to remove the dev features as it'll make the SDK non-functional in production
2. We should have different ProgramManager methods for dev node on second thought so that people know that these methods exist and we don't add any error to our existing methods.

[iamalwaysuncomfortable]

This actually needs to stay here :)

[iamalwaysuncomfortable]

A few nits below, can we also make a create-leo-app example that shows how to deploy and execute a program against a devnode with a Readme.md that shows how to set it up?

[iamalwaysuncomfortable]

Suggested change

	* import { AleoKeyProvider, ProgramManager, NetworkRecordProvider } from "@provablehq/sdk/mainnet.js";
	* import { AleoKeyProvider, getOrInitConsensusVersionTestHeights, ProgramManager, NetworkRecordProvider } from "@provablehq/sdk/mainnet.js";

[iamalwaysuncomfortable]

We should refactor these methods to use some common routines to reduce code duplication as this will become harder to maintain in the future, but this is approved for now in order to provide the functionality to outside users.