Adapt cmdline assert for nushell/nushell#15881

[CSharperMantle]

Related to nushell/nushell#15881.
Related to nushell/nushell#15889.

[github-actions]

Script Analysis

• The change modifies a path existence check to handle quoted commandline paths in Windows Terminal profiles
• Uses str trim --char '"' to properly handle quoted executable paths which is a common Windows Terminal configuration
• Maintains all existing assertions for profile validation
• Follows Nu's structured data handling approach by using get on the profile object

Security Review

• No direct security vulnerabilities introduced
• The change actually improves reliability by properly handling quoted paths which could previously cause false negatives
• No command injection risks as this is only checking path existence
• No sensitive data exposure in the assertions

Optimization Suggestions

• Consider using path expand in addition to str trim for more robust path handling
• Could potentially combine the path existence checks into a single pipeline for slightly better performance
• The change is already quite efficient as it uses built-in commands and maintains lazy evaluation

Overall Quality: 4 (The change is solid but could be slightly more robust with path expansion)

[CSharperMantle]

Are these workflows running against HEAD or the latest nightly artifacts?

[hustcer]

Are these workflows running against HEAD or the latest nightly artifacts?

They run against the latest nightly builds, and It's scheduled to run every morning, I have just started the nightly build workflow manually