Add wallJumpAvoid to strat and notable schema

[blkerby]

This addresses a long-standing issue (#1001) about marking strats that are only useful in walljumpless contexts. This PR just adds a new boolean property wallJumpAvoid to strats and notables, along with an example. Later PRs would go through and populate this throughout the logic.

Based on the discussion in the issue, one alternative that was considered was implementing a more general tag property. However, after thinking about this some more, it seems that a simple tag would not work well for the other examples mentioned in the issue. For example, to model a strat that softlocks you at an item location, we would want to model more information such as the specific item and/or tech that could get you out of the softlock. The existing "failures" schema is also relevant to modeling softlock risk, and we may want to refine/expand it someday, but a simple tag is again not going to be enough. And "patience" is already modeled through tech, so it seems unnecessary to model as a tag. A boolean property has the advantage of being a more structured format (compared to a bag of strings), making it more straightforward to consume.

The plan is to use these properties in Map Rando to help reduce the clutter on the Generate page as well as the logic pages. The notable property wallJumpAvoid would apply to filtering notables on the Generate page; initially we may simply filter out the walljumpless notables from showing there, though eventually we could add some control to toggle them on or off. The strat property wallJumpAvoid can be applied to filter strats on logic pages for rooms and tech, and we already have a place to add a toggle for that.

[osse101]

• Hopefully it is clear that a walljump being too difficult, whatever the tech level, still allows for easier alternative strats 😺

• I like what this change lets us do. And if there is a grouping structure in the future we want to use, I don't think that would be difficult to switch to.