[AURON #2364] fix: Native Paimon V2 scan returns wrong results with native filter

[lyne7-sc]

Which issue does this PR close?

Closes #2364

Rationale for this change

Auron recently added native scan support for Paimon DSv2 tables. When a Paimon V2 native scan is followed by a native filter, the query can return wrong results.

For example:

create table paimon.db.t_rename_columns (id int, v string) using paimon;
insert into paimon.db.t_rename_columns values (1, 'a'), (2, 'b');
select id from paimon.db.t_rename_columns where id = 1;

The buggy plan returns an empty result instead of [1].

What changes are included in this PR?

updates AuronConverters.needRenameColumns to mark NativePaimonV2TableScan as requiring rename-columns handling.

Are there any user-facing changes?

No API changes. Only a bug fix.

How was this patch tested?

Adds a Paimon V2 integration test covering a native filter on top of a native Paimon V2 scan.