[BugFix] Be crash while query information_schema.warehouse_queries (backport #72019)

[mergify]

Why I'm doing:

Table
information_schema.warehouse_queries and information_schema.warehouse_metrics

FE Side
WAREHOUSE_ID BIGINT on the FE side

BE Side
WAREHOUSE_ID VARCHAR on the BE side

Problem
Query these system tables triggered a type-mismatch assertion and crashed the BE(Debug compiled) with SIGABRT.

be/src/gutil/casts.h:100: To down_cast(From&) [with                                                                       
    To = const starrocks::FixedLengthColumnBase<long int>&;
    From = const starrocks::Column]:                                                                                                      
    Assertion `dynamic_cast<ToAsPointer>(&f) != NULL' failed.        
  *** Aborted at ... ***                                                                                                                  
  *** SIGABRT received by PID ...; stack trace: ***                  
      @  google::FailureSignalHandler(int, siginfo_t*, void*)
      @  raise
      @  abort
      @  __assert_fail
      @  down_cast<FixedLengthColumnBase<long> const&>(Column const&)
      @  FixedLengthColumnBase<long>::append(Column const&, ulong, ulong)
      @  NullableColumn::append(Column const&, ulong, ulong)
      @  ColumnHelper::copy_and_unfold_const_column(TypeDescriptor, bool, ..., int)
      @  ColumnHelper::move_column(TypeDescriptor, bool, ..., int)
      @  pipeline::UnionConstSourceOperator::pull_chunk(RuntimeState*)
      @  pipeline::PipelineDriver::process(...)
      @  pipeline::GlobalDriverExecutor::_worker_thread()

What I'm doing:

Thrift RPC
Keep using varchar WAREHOUSE_ID

FE & BE Side
Declare WAREHOUSE_ID as TYPE_BIGINT for information_schema.warehouse_queries and information_schema.warehouse_metrics

Fixes #issue

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function
  • This pr needs auto generate documentation
• This is a backport pr

Bugfix cherry-pick branch check:

• I have checked the version labels which the pr will be auto-backported to the target branch
  • 4.1
  • 4.0
  • 3.5
  • 3.4

---

This is an automatic backport of pull request #72019 done by [Mergify](https://mergify.com).