avs_pc: add wasm source map so avs debugging in chrome is possible

[EnricoSchw]

---

PR Submission Checklist for internal contributors

• The PR Title

  • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
  • contains a reference JIRA issue number like SQPIT-764
  • answers the question: If merged, this PR will: ... ³

• The PR Description

  • is free of optional paragraphs and you have filled the relevant parts to the best of your ability

---

What's new in this PR?

This PR adds a new option to create a WASM. This creates a source map and allows you to debug the AVS C code in the browser. It is a simple implementation. For More information i add a documentation file:

Issues

It is difficult to understand the behavior of the AVS Lib without a debugging infos in the browser.

Causes (Optional)

I debug how c objects work together with JS objects.

Solutions

Create a WASM with Debugging infos.

Pease check: README IN DOC

How to Test

Pease check: README IN DOC

---

PR Post Merge Checklist for internal contributors

• If any soft of configuration variable was introduced by this PR, it has been added to the relevant documents and the CI jobs have been updated.

---

References

1. https://sparkbox.com/foundry/semantic_commit_messages
2. https://github.com/wireapp/.github#usage
3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

[CLAassistant]

All committers have signed the CLA.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[z-dule]

This looks good to me.