Fix API_VERSION

[tabaktoni]

From @PhilippeR26

I received an interesting question : why ApiVersion and SpecVersion do not have the same type? Why an object on one side and a string on the other side?

types-js/src/wallet-api/components.ts

Lines 22 to 26 in 76a31d5

	/**
	* A Starknet RPC spec version, only two numbers are provided
	* @pattern ^[0-9]+\\.[0-9]+$
	*/
	export type SpecVersion = string;

types-js/src/wallet-api/components.ts

Lines 144 to 149 in 76a31d5

	/**
	* The version of wallet API the request expecting. If not specified, the latest is assumed
	*/
	export interface ApiVersion {
	api_version?: string;
	}

Honestly, the question is legit.

From @tabaktoni

1. Question ?
   _The second question I have here, and I can't remember what it is, is how developers correlate API_VERSION and SPEC_VERSION.

API_VERSION is the version of the API provided by the wallet (internally whatever), and it can be whatever let's say: 33.7.56
SPEC_VERSION is the version of the RPC Specification wallet provided, and It can be only one of the versions of the spec let's say: 0.7.1

Now, how do you correlate these two as there is no specification correlation is I guess wallets provide some table on their documentation saying:
API_VERSION SPEC_VERSION
33.7.56 | 0.7.1
33.7.55 | 0.7.1
33.7.53 | 0.7.1
33.7.32 | 0.7.0_

2. Fix
   But I think I could do:
   export type API_VERSION = string;

and

export interface ApiVersionRequest {
  api_version?: API_VERSION;
}

And avoid using ApiVersion NAME in this case i think all should be ok with naming collision

[PhilippeR26]

Wallet teams are interested to have rather quickly a new version of this lib, including the string types for both versions responses.