Update templates to include header in the README

What does this MR do?

Add updated export files for project templates. These include a header in the README to warn them that the project was imported.

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• [-] Documentation created/updated
• [-] API support added
• [-] Tests added for this feature/bug
• Review
  • [-] Has been reviewed by UX
  • [-] Has been reviewed by Frontend
  • Has been reviewed by Backend
  • [-] Has been reviewed by Database
• [-] Conform by the merge request performance guides
• [-] Conform by the style guides
• [-] Squashed related commits together

What are the relevant issue numbers?

Closes gitlab-org/gitlab-ce#36904

/cc @marin @briann @bikebilly

The fact that are templates are bundled in a tar.gz makes it hard to review. Is there a reason we didn't just include them as subdirectories?

@zj I didn't see a README in the express.tar.gz. Is it supposed to be there?

assigned to @zj

@stanhu Could you explain your findings?

HEADs I found:

project	bundle HEAD	project HEAD
express	85717752ab517ac61ce3d7c736a8745a3cc1439a	gitlab-org/project-templates/express@85717752
rails	42fa6f17077d601adbee9c63dd4044e29e1a9921	gitlab-org/project-templates/rails@42fa6f17
spring	b5f9057ca63c712c6b7ddb65bb2dfebc022e2c0b	gitlab-org/project-templates/spring@b5f9057c

All commits match the commit that actually included the readme?

assigned to @stanhu

I see where I was confused. I was expecting the .tar.gz to have the README.md, but instead the .bundle file did. How confusing. Can you create a separate issue on how we can avoid including binary files in our templates?

approved this merge request

merged

mentioned in commit 5f88660a

Picked into https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/14002, will merge into 9-5-stable ready for 9.5.3

mentioned in commit b79d6f20