[wasm] Test against head.

[lina128]

This PR has below changes:

1. Remove temporary solution because symlink won't be changed by release any more.
2. Add wasm to integration test.
3. Refactor package.json and cloudbuild.yml to be be consistent with other packages.
4. Add dependency to package_dependencies.json.

This change is 

[nsthorat]

Reviewed 6 of 6 files at r1.
Reviewable status: complete! 1 of 1 approvals obtained (waiting on @dsmilkov, @lina128, @nsthorat, @pyu10055, and @tafsiri)

---

tfjs-backend-wasm/package.json, line 24 at r1 (raw file):

    "cpplint": "./scripts/cpplint.js",
    "lint": "tslint -p . -t verbose && yarn cpplint",
    "test": "yarn && yarn build-deps && yarn build && karma start",

one thing i realized, this means every time you run test you have to build all the dependency projects. this can slow things down -- is there any way to split these up (for all packages)? fine to submit as is for now, just something to think about.

[dsmilkov]

Reviewed 6 of 6 files at r1.
Reviewable status: complete! 2 of 1 approvals obtained (waiting on @dsmilkov, @nsthorat, @pyu10055, and @tafsiri)

---

tfjs-backend-wasm/package.json, line 24 at r1 (raw file):

Previously, nsthorat (Nikhil Thorat) wrote…

one thing i realized, this means every time you run test you have to build all the dependency projects. this can slow things down -- is there any way to split these up (for all packages)? fine to submit as is for now, just something to think about.

maybe we can add "test-dev" or "test-fast" across all repos, used for development. In general I like that "yarn test" is doing all the things since now that everything is at master, we will likely touch several files across packages in the same commit/PR.

[lina128]

Reviewable status: complete! 2 of 1 approvals obtained (waiting on @dsmilkov, @nsthorat, @pyu10055, and @tafsiri)

---

tfjs-backend-wasm/package.json, line 24 at r1 (raw file):

Previously, dsmilkov (Daniel Smilkov) wrote…

maybe we can add "test-dev" or "test-fast" across all repos, used for development. In general I like that "yarn test" is doing all the things since now that everything is at master, we will likely touch several files across packages in the same commit/PR.

Thank you Nikhil and Daniel! Great suggestion. I can add a test-fast command for all repos in a separate PR.