[Enhancement] avoid redundant directory creation when create file block (backport #55716)

[mergify]

Why I'm doing:

After version 3.3, we support spilling operator intermediates to remote object storage. However, in the current implementation, every time a block is allocated, it checks whether the directory exists, resulting in unnecessary API calls and latency.

What I'm doing:

This pull request includes changes to the FileBlockManager class to optimize the creation of directories in the file block manager. The most important changes involve adding a check to avoid redundant directory creation and introducing a new member variable to track the last created directory.

Optimization of directory creation:

• be/src/exec/spill/file_block_manager.cpp: Added a check to ensure that the directory is only created if it has not been created before, reducing unnecessary filesystem operations. ([be/src/exec/spill/file_block_manager.cppR237-R240](https://github.com/StarRocks/starrocks/pull/55879/files#diff-3bb4fc69ffe78e61658f4b5aa8ac78514b11550a0c87a1781c33d6a9d19a5e02R237-R240))
• be/src/exec/spill/file_block_manager.h: Introduced a new member variable _last_created_container_dir to store the path of the last created directory, which is used in the aforementioned check. ([be/src/exec/spill/file_block_manager.hR51](https://github.com/StarRocks/starrocks/pull/55879/files#diff-80a364cbfceb51fff006948ceed1b690236ad393f2fca768cf22032eb88b34e9R51))

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