fix(market): write StorageVersion before Admin in initialize

[Akeem813]

Problem

The two storage writes in initialize() were ordered admin-first, version-second. If the transaction is interrupted between those two writes (out-of-gas or host error), the resulting partial state is different depending on which write completed:

Interrupted after	has_admin()	assert_version()	Result
set_admin (old ordering)	true	UpgradeRequired	Bricked: initialize() returns AlreadyInitialized, but all storage accessors return UpgradeRequired. No recovery path short of redeployment.
set_version (new ordering)	false	Ok(())	Recoverable: initialize() can be retried. All require_initialized guards still reject callers, so nothing can be called in the gap.

Fix

Swap the write order: call storage::set_version before storage::set_admin.

The AlreadyInitialized guard (has_admin() check) is unchanged — it still correctly rejects any second complete call to initialize() after a successful first run.

Why This Satisfies "Reject initialize twice"

The existing has_admin() guard already returns ContractError::AlreadyInitialized on a second call. This PR does not change that logic — it hardens the write ordering so that the guard's sentinel value (Admin) is only written once all preceding state is durable. A second initialize() call on a successfully initialized contract still returns AlreadyInitialized (#42).

Files Changed

• contracts/market/src/lib.rs — reorder set_version before set_admin inside initialize()

Acceptance Criteria

• Second initialize returns ContractError::AlreadyInitialized — existing guard, unchanged
• Partial-write recovery: interrupted init leaves contract in a retryable state, not a bricked one