chore: add .devcontainer configuration

[andoulla]

Description

Enable the ability to run the components repo in the remote env

Steps for opening in VS

• In a terminal SSH into your remote env
• Clone the repo
• Click the green bar(it maybe blue) in the bottom-left (“Dev Container: …“) and then choose “Reopen folder in SSH”
• Click open in container

[thomasdigby]

Should we make this repo private if we're adding custom Atom dev container stuff?

[andoulla]

Should we make this repo private if we're adding custom Atom dev container stuff?
@euanhunteratom what do you think?

[euanhunteratom]

Should we make this repo private if we're adding custom Atom dev container stuff?
@euanhunteratom what do you think?

Not sure tbh, more of a Tim question I think. The base image and the whole remote dev setup this relies on are private and don't think there is anything particularly proprietary in the files added to this branch. Not sure what the original rational for this repo being public was to weigh against.

License wise, I see there is the GPL license under lib/ but not at the top-level. Is the intention thus that the library itself is GPL but everything else is "proprietary but source available"? Maybe want an additional License file to clarify that but IANAL.