[release/7.0] [wasm] Fix JSExport on struct and records

[github-actions]

Backport of #74763 to release/7.0

/cc @maraf

Customer Impact

Fix using JSExport on structs, records and methods with expression body.

Testing

Unit test

Risk

None

IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Backport of #74763 to release/7.0

/cc @maraf

Customer Impact

Fix using JSExport on structs, records and methods with expression body.

Testing

Unit test

Risk

None

IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.

Author:	github-actions[bot]
Assignees:	-
Labels:	arch-wasm, area-System.Runtime.InteropServices.JavaScript
Milestone:	-

[carlossanlop]

@maraf@lewing@pavelsavara this PR was created at noon PDT yesterday. I am unsure if it was able to finish before the CI went down for maintenance, which was around 4pm PDT. Can you please verify that the CI results ran the necessary tests and they passed?

[carlossanlop]

Update: I was told the safe thing to do is to close and reopen PRs that may have been impacted by the system being down. The CI runs might have kept running during maintenance, but the results probably didn't flow to GitHub.

[carlossanlop]

All green now, with a proper amount of CI legs executed.
Approved and signed off.
Ready to merge.

[pavelsavara]

Would this merge show up in RC2 ? @maraf I think we need to merge it there as separate PR

[maraf]

Yes, it shows up in RC2.