Better handling for bad column selections about pointblank

[rich-iannone]

It's all good! There's so many moving parts here and you've navigated all of this really well. I do think the in-report💥 with those very cases would be ideal. We could even alter the error message that appears when hovering over the 💥 in this case. Thinking about this more deeply, I remember that serially() also offers pretty good safety measures for this sort of thing (e.g., check that column exists, then validate that column) but it's not great for checking multiple columns after the preliminary tests.

Thanks for getting further in the weeds on this part of the package!

[yjunechoe]

Sorry @rich-iannone for accidentally introducing some weird behavior during tidyselect integration 😅. But these are good to know! I agree that this is a good opportunity to modernize this while we're at it.

Just one follow-up Q: could we move forward treating columns = NULL the same as create_agent(exibble) |> col_vals_lt(columns = starts_with("z") and 💥 at report? Both would be a case of "you probably didn't mean to select 0 columns so we'll gently nudge you to specify columns or pair this selection attempt with active"

I'll think through some of these edgecases more and try to tackle this in a separate PR (after merging the documentation PR and getting tidyselect for has_columns()). I'll use this issue to dump some thoughts that come up in the meantime

[yjunechoe]

Closed by #499