Add workflow to sync templated repo from upstream on a schedule

[fredrikhgrelland]

https://github.com/narrowspark/template-sync-action

[zhenik]

Suggestion for each module that is created with the template:
1. rename branch master to upstream and leave it untouchable, only for sync with vagrant-hashistack-template
2. make new branch which is going to be the default branch

Once the original template is updated, the developer of the module decides the necessity of rebase upstream -> default

[zhenik]

@fredrikhgrelland can you elaborate more why it should be done on schedule?

Update 1

I faced an issue and sync on schedule is one of the solutions.

Case:

1. New linter v3.10.0 was released today
2. Some of our current PR in modules start failing because of new linter checks.
3. To be able continue we have to fix linter problems in original template
4. Downstream patch changes from vagrant-hasistack to vagrant-hashistack-template
5. Sync module with original-template

The current problem could be solved

1. Use concrete linter version in original template instead of latest (bump periodically)
   https://github.com/fredrikhgrelland/vagrant-hashistack/blob/master/.github/workflows/on_pr_master.yml#L37
2. Leave linter latest version schedule periodic sync vagrant-hasistack to vagrant-hashistack-template, and manual sync vagrant-hashistack-template -> module

[Neha-Sinha2305]

I would go with Option 1:

Use concrete linter version in original template instead of latest (bump periodically)
https://github.com/fredrikhgrelland/vagrant-hashistack/blob/master/.github/workflows/on_pr_master.yml#L37

[fredrikhgrelland]

Option 1 is always be the right one.

[fredrikhgrelland]

This is irrelevant becuase of #331 closing