Add a dataframe call matcher for linting tables

[pritishpai]

Changes

Current linting does not collect dataframe calls like df.write[.mode()].saveAsTable(). Adding a method to fix this issue.

Small fix for recent blueprint change for prompts.

[github-actions]

✅ 115/115 passed, 10 skipped, 1h26m34s total

_{Running from acceptance #8923}

[asnare]

This is an improvement, thanks. I'm happy to merge this.

Something to think about is that currently the detection misses a lot of common cases, because it assumes there will only be a single mode/format/option/partitionBy/bucketBy call between .write and .saveAsTable() whereas in practice a few of them are normally chained.

(Random thought: I think for .saveAsTable() only mode and option can be used?)

Anyway once you find the .write node,

You can solve that with recursion, once you have found .write, by checking the next node:

• If the node is .saveAsTable(), return True.
• If the node is one of {"mode", "format", "option", "partitionBy", "bucketBy"}, then return what these rules say about the next node (via recursion).
• Return False.

[pritishpai]

Something to think about is that currently the detection misses a lot of common cases, because it assumes there will only be a single mode/format/option/partitionBy/bucketBy call between .write and .saveAsTable() whereas in practice a few of them are normally chained.

Currently added a few more test cases, and it seems multiple chained calls are also being addressed.