feat: Add connected app credential workflow

[haifeng-li-at-salesforce]

Summary

• Add workflow nodes to prompt users for sensitive connected app information
• Fix login host property handling for all apps
• Enhance connected app metadata retrieval and selection

Changes

This PR includes the following commits:

1. feat: prompt the user for the sensitive information of the connected app (3fbc39b)
2. fix: login host is no longer a common property for all apps (069067f)

Key Updates

• Documentation: Updated mobile native app generation guide
• New Workflow Nodes:
  • checkConnectedAppListRouter - Routes based on connected app list state
  • checkConnectedAppRetrievedRouter - Routes based on connected app retrieval state
  • fetchConnectedAppList - Fetches available connected apps
  • retrieveConnectedAppMetadata - Retrieves metadata for selected connected app
  • selectConnectedApp - Handles connected app selection
• Enhanced Project Generation: Updated metadata handling for connected apps
• Removed: Deprecated environment validation nodes
• Tests: Added comprehensive tests for project generation

Files Changed

14 files changed with 976 additions and 140 deletions

Test Plan

• Tested connected app selection workflow locally
• Verified sensitive information prompting works correctly
• Confirmed login host property handling is correct for all apps
• All existing tests pass
• New project generation tests added and passing

[ben-zhang-at-salesforce]

noticed an issue manual testing it with 0 connected app configured on the server, the workflow completed right away when it detected no connected app configured. there are two solutions for it

1. it goes to failed complete with proper message like "configure your connect app on sever, and try again"
2. loop on the connect app credential collecting step: show the message and rerun the step when using typing back something like "continue", "try agin", "I configured the app on server"...

Personally I like option 2 due to it retry on the sport while option 1 restart from scratch which will requires user to re-enter packagename, company name...

[ben-zhang-at-salesforce]

looks good, manually tested, great job solving the client key and callback url issue.