Add automated propagation of changes to ssciwr/cpp-project-template

[thomasisensee]

We can now automatically propagate changes from this repo's main branch to the main branch of the cpp-project-template, as suggested by this issue. The workflow ran successfully (link) and created the commit: ssciwr/cpp-project-template@main...sync-test

The workflow bakes the project using the following configuration (up for discussion):

cookiecutter-cpp-project/.github/cpp-project-template.yml

Lines 1 to 17 in 0e1e99f

	default_context:
	project_name: "Your Project"
	remote_url: "None"
	project_slug: "your-project"
	full_name: "Your Name"
	license: "MIT"
	use_submodules: "No"
	header_only: "No"
	external_dependency: "None"
	github_acitons_ci: "Yes"
	gitlab_ci: "No"
	readthedocs: "Yes"
	doxygen: "Yes"
	cxx_minimum_standard: "20"
	python_bindings: "No"
	pypi_release: "No"
	codecovio: "Yes"

TODO:

• Possibly insert a header in the README to indicate that the cpp-project-template was generated from this cookiecutter
  EDIT: Added Acknowledgement of cookiecutter at README's end
• Use the main branches instead of the test branches

cookiecutter-cpp-project/.github/workflows/sync-template.yml

Lines 3 to 6 in 0e1e99f

	on:
	push:
	branches:
	- sync-project-template

cookiecutter-cpp-project/.github/workflows/sync-template.yml

Line 42 in 0e1e99f

ref: sync-test

cookiecutter-cpp-project/.github/workflows/sync-template.yml

Line 59 in 0e1e99f

git push origin sync-test

[lkeegan]

thanks @thomasisensee this looks good to me! definitely an improvement to automatically sync changes from the cookiecutter to this template.

one question about catch2 - do we need to install it in CI if we're using fetchcontent in cmake? (I guess this might be more of a question for the cookiecutter than for your PR though)

[thomasisensee]

Valid point @lkeegan, we should decide on one option and either install Catch2 manually or via FetchContent. But as you said, I'd rather make this change in PR #135.