FOR REVIEW ONLY: java-algorand-sdk 2.11.0 changelog and version bump

Automatically generated by python-semantic-release

Seems to have been a bug in the changelog generator, so I have manually
written the notes using the same format

* Regenerate code from specification file

* feat: remove dry run due to removal in algod

* WIP: ignore falcon tags

Should ideally merge
https://github.com/algorand/algorand-sdk-testing/pull/327 first so we
can continue to use master

* test: revert algorand-sdk-testing branch to master

This will fail CI until
https://github.com/algorand/algorand-sdk-testing/pull/327 is merged

---------

Co-authored-by: Algorand Generation Bot <codegen@algorand.com>

AVM v13 relaxes box isolation: an app can opt its boxes into reads by any other
app. Both registries now do that in a new createApplication, which runs
app_params_set(appForeignBoxReads, true). Verified on localnet that the opcode is
permitted during the creating call itself, so no separate post-create step is
needed - the v13 notes describe enabling access as update-then-run, but that is
for apps already deployed.

Reads only; writes stay exclusive to the owning app. app_params_set is run by an
app on itself, so a contract that is not updatable can never opt in later, which
is what preserves intentional immutability.

The create is a real ABI method rather than a bare one. It lands in the ARC-56 and
the generated clients, it can take arguments later without changing the create
shape a second time, and it matches the house style - FracDelegationInstance
already has an ABI createApplication invoked by selector from the registry
factory. Both createRegistry paths switch from create.bare() to the method call;
every other caller routes through createRegistry.

Two consequences of the create no longer being bare, both found by the suite:

- deployRegistryWithoutBytecode in the period e2e spec deploys a registry
  directly and was still doing a bare create, which is no longer routed and fails
  with an err on the OnCompletion match.

- The ATST unit specs. ATST holds a contract with any create method in
  `isCreating` and rejects every ABI call with "method can not be called while
  creating" until a create method runs - but ATST 1.2.0 predates v13 and cannot
  execute app_params_set, so the real body cannot run in the emulator. The
  registry test subclass overrides createApplication with a no-op and calls it
  after construction; the opt-in itself is covered e2e.

Follow-up worth taking: with foreign reads on, much of the registries' readonly
getter and log-dumping surface (getDelegation, getPeriodSummary, logCommitteePages,
getEscrow, ...) exists only because cross-app box reads used to be impossible.
Not touched here.

Suite green: 539 passed (2 new).

uploadPeriodApproval/uploadInstanceApproval now take page1/page2/page3, and the
two per-page length asserts are gone from both.

The asserts (page.length <= 4096, ERR:AP_LN) could never fire: the network
rejects any application argument over 4096 bytes before the program runs, so an
over-long page never reaches them. errApprovalPageTooLong goes with them -
nothing else raised it.

A third page raises what the ABI can carry from 8188 to 12282 bytes of program -
a page holds 4094, not 4096, because an ARC-4 byte[] spends 2 bytes on its
length prefix - which is the room an approval program needs once it grows into
v13's 7 extra program pages. Trailing pages may be empty; each non-empty page is
written at the running offset, so the split points still carry no meaning.

The SDK wrappers pass an empty page3 for now. Two ceilings bind before it can be
filled: createPeriod/createInstance read the approval box back as two 4096-byte
pages, and a single app call can only buy 8 box references - 8192 bytes of box
write budget - so a larger upload needs the write split across more app calls
first.

Ran: frac-delegation suite (246 passed), ggov-registry admin + periods (43
passed). Full suite not re-run.