update createAsyncTransform to allow for different node types

[tmarmer]

Change Type (required)

Indicate the type of change your pull request is:

• patch
• minor
• major
• N/A

Does your PR have any documentation updates?

• Updated docs
• No Update needed
• Unable to update docs

Release Notes

• Update the createAsyncTransform util to consider different incoming node types coming from getNestedAsset option. Originally, this assumed that it would always be an asset node type and would asset-wrap the node, but to allow for some additional flexibility, the following rules are applied:
  • Asset nodes and Applicability nodes with a value that is an asset node get asset wrapped like before.
  • multi-nodes have their values spread into the initialized multi-node to keep the structure flat
  • everything else gets added to the initialized multi-node as-is.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.87%. Comparing base (f748126) to head (181e4ff).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #708   +/-   ##
=======================================
  Coverage   86.86%   86.87%           
=======================================
  Files         502      503    +1     
  Lines       25643    25660   +17     
  Branches     2624     2630    +6     
=======================================
+ Hits        22275    22292   +17     
  Misses       3045     3045           
  Partials      323      323           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[KetanReddy]

Looks good! Just one small think about mocking in tests.