feat(wasm): Unconditionally parse instruction addresses

[lforst]

Currently we are only setting the platform and instruction_addr for a wasm frame if we find a matching debug image. This is not always the case and unconditionally parsing the instruction address is almost always desirable.

[lforst]

That's the one wasm PR for the year. We can pack it up.

[AbhiPrasad]

What motivated this change?

[lforst]

What motivated this change?

@AbhiPrasad A user wrote in via sales that the stack frames for an unsymbolicated wasm are all collapsed in the event. This is because for unsymbolicated wasm we parse out the module, but don't include the address:

  [{
    "module": "WASM/redacted/redacted",
    "filename": "/WASM/redacted/redacted.wasm:wasm-function[127458]:0x3695e9b",
    "abs_path": "https://redacted.com:3000/WASM/redacted/redacted.wasm:wasm-function[127458]:0x3695e9b",
    "in_app": true
  },
  {
    "module": "WASM/redacted/redacted",
    "filename": "/WASM/redacted/redacted.wasm:wasm-function[2275]:0x2b880f",
    "abs_path": "https://redacted.com:3000/WASM/redacted/redacted.wasm:wasm-function[2275]:0x2b880f",
    "in_app": true
  },
  {
    "module": "WASM/redacted/redacted",
    "filename": "/WASM/redacted/redacted.wasm:wasm-function[79547]:0x21df74d",
    "abs_path": "https://redacted.com:3000/WASM/redacted/redacted.wasm:wasm-function[79547]:0x21df74d",
    "in_app": true
  }]

The product will show the stack frames all collapsed because it takes only the module (which in normal circumstances is a some .js and also has line & col). We are basically missing the address as a discriminating factor.