Task matching fails silently when the cycle point does not exactly follow [scheduler]cycle point format

[MetRonnie]

Steps to reproduce the bug

# flow.cylc
[scheduler]
    UTC mode = True
    allow implicit tasks = True
[scheduling]
    runahead limit = P1
    initial cycle point = 2000
    [[graph]]
        P1Y = foo

(The default cycle point format is CCYYMMDDThhmmZ)

$ cylc play myflow --pause
$ cylc hold myflow//20000101T00Z  # Note the minute is not specified

The workflow log says

INFO - Command succeeded: release(['20000101T00Z/foo'])

as if it worked. And TUI shows the task as held.

But the subtle giveaway that it did not work is that you don't get

INFO - [20000101T0000Z/foo waiting(held)(runahead) job:00 flows:1] => waiting(held)

Additional context

The string match here looks like the problem.

cylc-flow/cylc/flow/id_match.py

Lines 177 to 178 in aa01d96

	if not match(str_cycle, cycle):
	continue

I think we should try matching ISO8601Points or metomi.isodatetime.data.TimePoints (but need to take care to still match globs).

This bug does not occur for holding future cycle points