Add pass to conditional planner

[LForchini]

Fixes #251

Proposed Changes

• Add pass to the conditional move planner

Is there a nicer way to localise the pass message than the check I used? I considered having the prettyCoord function return undefined when given invalid moves instead of the string pass.

I'd also like some feedback on the UI here:

[github-actions]

Uffizzi Preview deployment-52912 was deleted.

[benjaminpjones]

Looks good to me!

I considered having the prettyCoord function return undefined when given invalid moves instead of the string pass.

I wouldn't change it, or at least I think the current behavior (and the way you handle it) is okay. It doesn't make a huge difference what we return in the "invalid" case, but at least now it prints out something reasonable in cases where we haven't explicitly handled it. E.g. the Joseki tool

I'd also like some feedback on the UI here

This one's tough, I can't think of anything better than this. Maybe other people will have feedback...

[BHydden]

I think it looks tidy. OGS is renowned for having noone on the team especially gifted at UI/UX 😅 so tidy and consistent seem adequate goals to aim for...

[anoek]

Thanks!