[BugFix] fix stack use after scope when get extra file size

[luohaha]

Why I'm doing:
When in ASAN mode, we find that BE crash because stack use after scope:

==2519==ERROR: AddressSanitizer: stack-use-after-scope on address 0x7f655d1a9750 at pc 0x00000ac2e06b bp 0x7f655d1a95f0 sp 0x7f655d1a95e8
READ of size 8 at 0x7f655d1a9750 thread T4331
   #0 0xac2e06a in std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::length() const /opt/rh/gcc-toolset-10/root/usr/include/c++/10.3.0/bits/basic_string.h:908
   #1 0xad8aab2 in std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::reserve(unsigned long) /opt/rh/gcc-toolset-10/root/usr/include/c++/10.3.0/bits/basic_string.tcc:284
   #2 0x1af62f3a in std::filesystem::__cxx11::path::operator=(std::filesystem::__cxx11::path const&) ../../../.././libstdc++-v3/src/c++17/fs_path.cc:457
   #3 0x1af53f8c in std::filesystem::__cxx11::_Dir::_Dir(std::filesystem::__cxx11::path const&, bool, std::error_code&) ../../../.././libstdc++-v3/src/c++17/fs_dir.cc:51
   #4 0x1af53f8c in std::filesystem::__cxx11::directory_iterator::directory_iterator(std::filesystem::__cxx11::path const&, std::filesystem::directory_options, std::error_code*) ../../../.././libstdc++-v3/src/c++17/fs_dir.cc:135
   #5 0xafaf18f in std::filesystem::__cxx11::directory_iterator::directory_iterator(std::filesystem::__cxx11::path const&) /opt/rh/gcc-toolset-10/root/usr/include/c++/10.3.0/bits/fs_dir.h:387
   #6 0x1323a519 in starrocks::TabletUpdates::_get_extra_file_size(long*, long*) const /root/celerdata/be/src/storage/tablet_updates.cpp:2888

What I'm doing:

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 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
  • 3.2
  • 3.1
  • 3.0
  • 2.5

[github-actions]

[FE Incremental Coverage Report]

✅ pass : 0 / 0 (0%)

[github-actions]

@Mergifyio backport branch-3.2

[github-actions]

@Mergifyio backport branch-3.1

[mergify]

backport branch-3.2

✅ Backports have been created

• #39740 [BugFix] fix stack use after scope when get extra file size (backport #39704) has been created for branch branch-3.2

[mergify]

backport branch-3.1

✅ Backports have been created

• #39741 [BugFix] fix stack use after scope when get extra file size (backport #39704) has been created for branch branch-3.1

[github-actions]

[BE Incremental Coverage Report]

❌ fail : 1 / 4 (25.00%)

file detail

	path	covered_line	new_line	coverage	not_covered_line_detail
🔵	be/src/storage/tablet_updates.cpp	1	4	25.00%	[2938, 2941, 2944]