SNOW-2430412: attributes copied for selectable and create deterministic CTE name to reduce describe query

[sfc-gh-aling]

1. Which Jira issue is this PR addressing? Make sure that there is an accompanying issue to your PR.

   Fixes SNOW-NNNNNNN

2. Fill out the following pre-review checklist:

   • I am adding a new automated test(s) to verify correctness of my new code
     • If this test skips Local Testing mode, I'm requesting review from @snowflakedb/local-testing
   • I am adding new logging messages
   • I am adding a new telemetry message
   • I am adding new credentials
   • I am adding a new dependency
   • If this is a new feature/behavior, I'm adding the Local Testing parity changes.
   • I acknowledge that I have ensured my changes to be thread-safe. Follow the link for more information: Thread-safe Developer Guidelines
   • If adding any arguments to public Snowpark APIs or creating new public Snowpark APIs, I acknowledge that I have ensured my changes include AST support. Follow the link for more information: AST Support Guidelines

3. Please describe how your code solves the related issue.

two changes:

1. the current cte optimization would copy the original plan without copying attributes, and it leads to sending extra describe queries when solving conflicting column alias, which can potentially leads to performance regression.

under the parameter protection of CTE optimization and reduce describe query, we copy attributes when copying a snowflakeplan

2. in CTE optimization, we create a deterministic CTE table name given a query under the parameter protection of reduce desc query and snowpark connect mode, otherwise whenever dataframe.query is called, we will create a new CTE table name for the same dataframe, thus sending extra query to resolve attributes.

this is a pattern identified in snowpark connect that the protobuf of the same spark DF can be parsed multiple times (analyzePlan and execute), leading to dataframe.query is called multiple times, generating different CTE tables