fix: further improvements in simulate response v2 parser

[aorumbayev]

Fixes algorandfoundation/algokit-avm-vscode-debugger#57 and algorandfoundation/algokit-avm-vscode-debugger#58

[aorumbayev]

@lempira will test the cd pipeline on a fork more thoroughly tomorrow, its largely reusing the algokit-utils-ts setup.

[aorumbayev]

@lempira @neilcampbell should i change the version back to 0.1.0 given that we will be publishing to a new package and it wouldn't make sense to be consistent with Inc's versioning?

[neilcampbell]

@lempira @neilcampbell should i change the version back to 0.1.0 given that we will be publishing to a new package and it wouldn't make sense to be consistent with Inc's versioning?

@aorumbayev Inclined to continue on from their version, so that if the other package is deprecated, it's simply a change to the package name to switch over for other potential consumers.

[aorumbayev]

@lempira @neilcampbell should i change the version back to 0.1.0 given that we will be publishing to a new package and it wouldn't make sense to be consistent with Inc's versioning?

@aorumbayev Inclined to continue on from their version, so that if the other package is deprecated, it's simply a change to the package name to switch over for other potential consumers.

Alright, i pinned the current one to 0.3.0 via manual release here https://github.com/algorandfoundation/algokit-avm-debugger/releases/tag/v0.3.0, the semantic releases will kick off first npm publish as 0.3.1, hence continuing the versioning from original repo (cc @lempira )

[lempira]

@lempira @neilcampbell should i change the version back to 0.1.0 given that we will be publishing to a new package and it wouldn't make sense to be consistent with Inc's versioning?

@aorumbayev Inclined to continue on from their version, so that if the other package is deprecated, it's simply a change to the package name to switch over for other potential consumers.

Alright, i pinned the current one to 0.3.0 via manual release here https://github.com/algorandfoundation/algokit-avm-debugger/releases/tag/v0.3.0, the semantic releases will kick off first npm publish as 0.3.1, hence continuing the versioning from original repo (cc @lempira )

I like the idea of continuing the version number as well