contributing-device-support.md: Rework repo transfer and autokit requ…

[floion]

…irement steps

Change-type: patch

---

Contributor checklist

• [ ] Changes have been tested
  • [ ] Covered in automated test suite
  • [ ] Manual test case recorded
• [ ] Change-type present on at least one commit
• [ ] Signed-off-by is present
• [ ] The PR complies with the Open Embedded Commit Patch Message Guidelines

Reviewer Guidelines

• When submitting a review, please pick:
  • 'Approve' if this change would be acceptable in the codebase (even if there are minor or cosmetic tweaks that could be improved).
  • 'Request Changes' if this change would not be acceptable in our codebase (e.g. bugs, changes that will make development harder in future, security/performance issues, etc).
  • 'Comment' if you don't feel you have enough information to decide either way (e.g. if you have major questions, or you don't understand the context of the change sufficiently to fully review yourself, but want to make a comment)

[floion]

@balena-ci I self-certify!

[floion]

@resin-jenkins test this please

[floion]

@resin-jenkins test this please

[vipulgupta2048]

I thought in the past, Docs changes could have skip ci, and they could be forced to merge so we do not have to go through all the testing. Is that still the process we follow?