ci: Move ios-12-5-1-x86-64-coreml to periodic

[seemethere]

Stack from ghstack:

• -> ci: Move ios-12-5-1-x86-64-coreml to periodic #80455

Moves these jobs to periodic, no one currently supports these jobs and
they do take up limited macOS resources so moving to periodic for now.

Signed-off-by: Eli Uriegas eliuriegas@fb.com

[facebook-github-bot]

🔗 Helpful links

• 🧪  See artifacts and rendered test results at hud.pytorch.org/pr/80455
• 📄  Preview Python docs built from this PR
• 📄  Preview C++ docs built from this PR
• ❓Need help or want to give feedback on the CI? Visit our office hours

✅ No Failures (0 Pending)

As of commit 8c1c3cd (more details on the Dr. CI page):

Expand to see more

---

💚 💚 Looks good so far! There are no failures yet. 💚 💚

---

This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

[seemethere]

@pytorchbot merge -f

[seemethere]

Merging without CI since this is just moving a workflow to another workflow

[pytorchmergebot]

@pytorchbot successfully started a merge job. Check the current status here

[pytorchmergebot]

@seemethere your PR has been successfully merged.

[github-actions]

Hey @seemethere.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.