Public nodes can disable API auth. Always setting X-Algo-API-Token to an
empty string caused those requests to fail. Only send the header when
both the header name and token are non-empty.

Fixes #653.

Closes algorandfoundation/algorand-typescript-testing#145

Fail locally with the leftover token names instead of sending
unsubstituted TMPL_* integers to algod (ParseUint invalid syntax).

Closes #424.

A logic signature authorizes a transaction with a program instead of a key. The
program either owns its own account, whose address is the hash of the program, or
is delegated by an account that signs it and spends from its own balance.

SignedTransaction gains an lsig field, so a logicsig-signed transaction now
survives a decode and re-encode instead of silently losing its authorization.

Delegation targets lmsig. Consensus v41 rejects the legacy msig field on a
LogicSig, because it hashed the bare program under the same domain separator a
single-key delegation uses, letting a member's subsignature be lifted out and
replayed as their own personal delegation. lmsig binds the multisig account
address into the signed bytes. The msig field is kept so historical transactions
decode, but nothing produces it.

The block template declared its own opaque lsig field beside the flattened
SignedTransaction, which would have shadowed the real one. Removed there and
added to both generator constructors; algod_client/tests/models.rs pins that a
logic signature reaches the flattened type, and lives outside src/ so it survives
regeneration.

The escrow address test uses the known program and address pair from the
js-algorand-sdk suite rather than a locally computed value.

An all-zero signature is the absent signature on the wire — go-algorand drops it
via MsgIsZero(), and js-algorand-sdk treats an all-zero fixed-length array as a
default value and skips it. We were writing the 64 zero bytes, producing a blob
no other implementation sends and inflating estimate_size along with any fee
derived from it. The transaction id is unaffected, since it hashes the
transaction rather than the envelope.

The skip predicate now covers absent-or-all-zero, applied to the transaction
signature and to multisig subsignatures, where a participant who has not signed
yet would otherwise leave a zero-filled placeholder on the wire.

Test scaffolds that used a zero signature as a stand-in were exercising nothing
once it stopped being encoded, so they now use a non-zero placeholder — same
encoded length, so the length assertions still hold.

Ships the tested upgrade script so clusters carried through pg_upgrade at
0.2 can reach 1.0 with ALTER EXTENSION pg_algorand UPDATE, without the
drop/recreate dance. CREATE OR REPLACE upgrades the two functions with
dependents in place; the three GetNFD* functions are dropped and
recreated because 1.0 renamed their parameters. Verified on betanet,
testnet x2 and mainnet upgrades (identical to a fresh 1.0 install).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019ACfCvu2UPpd6UcoK8cpW3

Feat/global avm protocol ver update

- Introduced Falcon-1024 account type with corresponding UI elements and localization in Russian, Slovak, and Turkish.
- Implemented account creation, import, and export functionalities for Falcon accounts.
- Added Falcon-specific mnemonic generation and validation.
- Integrated Falcon signing mechanism for transactions.
- Updated routing to include Falcon account creation page.
- Enhanced backup warnings and account management features for Falcon accounts.
- Added unit tests for Falcon account functionalities.