fixes for the wasm build

[khieta]

Description of changes

While working on #854 I realized that the wasm build was not actually generating valid TypeScript (largely due to changes I made for #757). This PR fixes the issues & adds CI to avoid this mistake in the future.

Detailed summary:

• Fixes the bad TypeScript by adjusting various tsify annotations
• Adds CI to check that the generated TypeScript is valid
• Adds #![cfg_attr(feature = "wasm", allow(non_snake_case))] in a few files to suppress annoying VSCode warnings
• Removes the cedar-wasm/src/{validator, authorizer}.rs files since it's simpler to expose the FFI functions directly rather than introduce a trivial wrapper

Issue #, if available

Checklist for requesting a review

The change in this PR is (choose one, and delete the other options):

• A change (breaking or otherwise) that only impacts unreleased or experimental code.

I confirm that this PR (choose one, and delete the other options):

• Does not update the CHANGELOG because my change does not significantly impact released code.

I confirm that cedar-spec (choose one, and delete the other options):

• Does not require updates because my change does not impact the Cedar formal model or DRT infrastructure.

[khieta]

Still need to investigate the new wasm-example failure, but the PR is otherwise ready for review.

Update: I believe the issue is downstream in cedar-examples. Looks like an error in the tests wasn't being caught due to the borked TypeScript. (Will fix after this PR is merged.)

[john-h-kastner-aws]

Seems legit