dev: adding a command for creating a dev environment in codespaces from cli

[Bryce-Soghigian]

Description
I find that I end up creating a codespace after doing some code changes as it requires me to jump into the browser, so I run CI etc after creating a PR.

This change adds a basic command to launch a codespace inside of vscode with codespace branch="branch-name" so that I have one setup and initialized from the moment I start working.

How was this change tested?
make codespace BRANCH=feature-name

Does this change impact docs?

• Yes, PR includes docs updates
• Yes, issue opened: #
• No

Release Note

[tallaxes]

I find that I end up creating a codespace after doing some code changes as it requires me to jump into the browser, so I run CI etc after creating a PR.

I am not sure I understand your workflow. You know you can switch branches (and/or PRs) in codespace, right? While there are some use cases for creating more than one codespace, having one per branch is not expected to be a very common workflow needing automation.