Add issue templates for code synchronization

[israel-hdez]

What this PR does / why we need it:

The issue template covers both synchronization with upstream repositories, and also manifest replication to odh-manifest repository.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Related to opendatahub-io/modelmesh-serving#188

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: israel-hdez

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [israel-hdez]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[spolti]

@israel-hdez does it still valid?

[israel-hdez]

@spolti I know @heyselbi has a document that may cover this. I'll defer to her the decision to either merge or close.

[spolti]

Apparently the change looks good, however, wouldn't be better to use the README or another .md file instead a template?

[israel-hdez]

Apparently the change looks good, however, wouldn't be better to use the README or another .md file instead a template?

Hmm... So, this PR has been here for some time.
My intention was to let people create a GitHub issue from the template and add that ticket to the board for work tracking. Then, people would tick the checkboxes in the ticket as progress is done.

But now that we moved back to Jira, an issue template no longer makes sense. So, you are right.

Well... @spolti you already have done a few code syncs. I think if you find the content useful, I can rework the PR to be a simple md file. Else, if you think the content is no longer relevant, let's simply close.

[spolti]

@israel-hdez I think we can keep it, it is useful for new contributors.

[spolti]

/retest