Improve the parser syntax about bos-workspace HOT 2 CLOSED

Yeah, glad you've brought this up.

The current format, including for app account (/@AppAccount/), can be hard to type/remember, as well as, since it is a essentially a comment format, commenting out a code block containing it can lead to a poor experience; it'll comment the first part, uncomment the alias, etc...

bos-loader's replacement strategy recognizes {REPL_KEY}, which works pretty well although (I've heard, but not experienced myself) it can cause some issues with syntax highlighting. This is the strategy used by DevHub and Near Discovery, adopting it would be easiest migration for them if they chose to do it.

I like using the @ for syntax highlighting, especially for skip.

from bos-workspace.

From conversation and to have parity with bos-loader, we should use ${} for replacements

from bos-workspace.