GridClient:Dynamic_SingleVM: enhance the script

[0oM4R]

Description

the issue maybe related to the network name; at that run that there is another network with the same name but not configured to support myceluim; this should be solved in #3822
but currently we enhanced the script and the workflow is passed
support features and ping node

Changes

• add myceluim configuration
• add features to the node qurey
• use pingNode to select a reachable node

Related Issues

#3834

Tested Scenarios

deployed a dynamic single vm on qa

• triggired the workflow on this branch : https://github.com/threefoldtech/tfgrid-sdk-ts/actions/runs/13051502010

https://github.com/threefoldtech/tfgrid-sdk-ts/actions/runs/13051502010/job/36412609964 qa workflow passed

Documentation PR

For UI changes, Please provide the Documentation PR on info_grid

To consider

Preliminary Checks:

• Preliminary Checks
  • Does it completely address the issue linked?
  • What about edge cases?
  • Does it meet the specified acceptance criteria?
  • Are there any unintended side effects?
  • Does the PR adhere to the team's coding conventions, style guides, and best practices?
  • Does it integrate well with existing features?
  • Does it impact the overall performance of the application?
  • Are there any bottlenecks or slowdowns?
  • Has it been optimized for efficiency?
  • Has it been adequately tested with unit, integration, and end-to-end tests?
  • Are there any known defects or issues?
  • Is the code well-documented?
  • Are changes to documentation reflected in the code?

UI Checks:

• UI Checks
  • If a UI design is provided/ does it follow it?
  • Does every button work?
  • Is the data displayed logical? Is it what you expected?
  • Does every validation work?
  • Does this interface feel intuitive?
  • What about slow network? Offline?
  • What if the gridproxy/graphql/chain is failing?
  • What would a first time user have a hard time navigating here?

Code Quality Checks:

• Code Quality Checks
  • Code formatted/linted? Are there unused imports? .. etc
  • Is there redundant/repeated code?
  • Are there conditionals that are always true or always false?
  • Can we write this more concisely?
  • Can we reuse this code? If yes, where?
  • Will the changes be easy to maintain and update in the future?
  • Can this code become too complex to understand for other devs?
  • Can this code cause future integration problems?

Testing Checklist

• Does it Meet the specified acceptance criteria.
• Test if changes can affect any other functionality.
• Tested with unit, integration, and end-to-end tests.
• Tested the un-happy path and rollback scenarios.
• Documentation updated to meet the latest changes.
• Check automated tests working successfully with the changes.
• Can be covered by automated tests.

General Checklist

• Tests included
• Build pass
• Documentation
• Code format and docstring
• Screenshots/Video attached (needed for UI changes)

[samaradel]

got this error even my twin id is verified

[0oM4R]

got this error even my twin id is verified

not sure but it is not related at all, Please try again with another twin and if issue still exists, open an issue;
and for the current issue, the workflow passes on qa

[maayarosama]

Should we exclude node 11 for now so the test can pass on Devnet?

[amiraabouhadid]

remove unused import generateRandomHexSeed