Early exit on column normalisation to improve DataFrame performance

[blaginin]

Which issue does this PR close?

Related to #14563 (probably more prs to come)

Rationale for this change

Now, when normalizing the column, we always generate plan.using_columns() which is recursive and very expensive - and may not be needed if column is already normalized

What changes are included in this PR?

Exit early if column already has a relation set. Also, set the relation when with_column_renamed is called

Are these changes tested?

Extended a test to assert references

Are there any user-facing changes?

No

[blaginin]

Got +38% increase in dataframe benchmark

 before after
with_column_10 769.06 µs 673.32 µs
with_column_100 1.4952 s 978.43 ms
with_column_200 36.544 s 26.682 s

[alamb]

FYI @Omega359

[Omega359]

I'll check this out tomorrow. we've been chatting about our approaches on #14563

[Omega359]

I think this is a reasonable change. I think it could be incorporated into my upcoming PR to enhance things a bit, especially since I think it may help other dataframe functions such as select(exprs)

[blaginin]

Nice thank you! But let's maybe keep PRs atomic? I plan to do one more (the one I described as a third in the issue), I don't think they overlap with each other?

[Omega359]

Of course we can have them atomic :)

[timsaucer]

This looks like a no brainer performance boost. Thanks!

[alamb]

This looks like a no brainer performance boost. Thanks!

I agree -- thank you @blaginin@timsaucer and @Omega359

🚀