[chore](build) Use include-what-you-use to optimize includes (PART II) (#18761)

Currently, there are some useless includes in the codebase. We can use a tool named include-what-you-use to optimize these includes. By using a strict include-what-you-use policy, we can get lots of benefits from it.

be/src/io/cache/file_cache.cpp

@@ -17,12 +17,25 @@
 
 #include "io/cache/file_cache.h"
 
+#include <fmt/format.h>
+#include <glog/logging.h>
+#include <string.h>
+
+#include <algorithm>
+#include <filesystem>
+#include <list>
+#include <ostream>
+#include <set>
+#include <utility>
+
 #include "common/config.h"
 #include "common/status.h"
 #include "gutil/strings/util.h"
+#include "io/fs/file_system.h"
+#include "io/fs/file_writer.h"
 #include "io/fs/local_file_system.h"
-#include "io/fs/local_file_writer.h"
-#include "olap/iterators.h"
+#include "runtime/exec_env.h"
+#include "util/string_util.h"
 
 namespace doris {
 using namespace ErrorCode;