Add Remote Development Blueprint

What does this MR do and why?

View the published blueprint at https://docs.gitlab.com/ee/architecture/blueprints/remote_development/

As a result of our ongoing Category:Remote Development Spike, we want to formalize the ongoing work and results via a Blueprint as outlined in the architecture workflow guide.

• https://gitlab.com/gitlab-com/create-stage/editor/-/issues/85

Item	Done
Determine with your manager whether to invoke the workflow.	✅
Start writing a blueprint somewhere! Depending on whether the content can be considered SAFE or not you may want to do that in a private space first.	✅
Involve Architecture Evolution Coach, a Principal+ Engineer who will support you throughout the process.	✅
Post a link to your blueprint in the internal #architecture channel on Slack.	✅
Open an architecture evolution blueprint merge request if you have not done it already.	✅
Work with Architecture Evolution Coach, a Product Manager, Engineering Manager, and Domain Experts to get the blueprint properly reviewed, commented, refined, and eventually merged!	TBA

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.