fix: duplicate templates to new paths to avoid component name clashes

Part of #31

Copies the current templates to new locations to avoid future name clashes as we migrate from CI includes to CI Components.

This is step 1 from the high-level plan to migrate to CI Components, as laid out in #31 (comment 2548285874)

1. Start copying the template/*.yml files into new subdirectories template/*-build/.
2. This will allow projects to start using components, eg component: $CI_SERVER_FQDN/gitlab-com/gl-infra/common-ci-tasks/standard-build@v2.77
3. Also copy the individual templates in /*.yml to subdirectories under template to allow projects to migrate to CI Components.
4. Start migrating projects from existing include to new component: approach. We can probably use https://gitlab.com/gitlab-com/gl-infra/common-template-copier to automate the migration of projects to the new components
5. Address any incompatibilities and issues as they arise. Since the original files are all in place, this should be possible to do as a gradual migration.
6. Once we understand the incompatibilities, set a deadline for migrating over to components.
7. After the cutoff, migrate all the templates to their new locations.
8. Consider publishing the components in the catalog, although we must stress that these components are intended for GitLab internal consumption only, not general consumption.