Replace a variable's type from `size_t` to `uint64_t`
to avoid warnings on 32-bit platforms.

The variable is the output of a hashing function and
undergoes shifting by 32 bits as the seeding step of
a hash combination between the two-halves of a
64-bit value.

The change has no functional impact.

This commit adds the initial implementation of the code-squashing
approach for AD. Users can now squash their models into a single
function that can then be used for evaluation, derivative calculation,
minimization, etc. through the RooFuncWrapper.

[windows] Fix building freetype, tbb and gtest in Debug mode with debug runtime libraries on Windows

Allows to configure different bins width for X and Y projections

fix several warnings from openui5

Let draw both left and bottom panels.
Try to catch resize of bottom panel to resize left panel at the same
time

reduce the use of locks in TPluginHandler and add fast path to ExecPlugin when type matching can be guaranteed

When some column types were specified explicitly by the user, RCsvDS
forgot to add that type to fColTypesList, which in turn caused
RCsvDS::SetEntry to skip the proper loading of some column data.

This fixes #12520.

The "Height" column is actually a double, it's surprising to
tell the datasource it's a string. Use "Name" as a string instead.

This is a test for #12520.

They should be stored in a vector corresponding to the sample, not in a
local variable that will not be reused later.

It's more efficient and also clearer from an ownership perspective if
all objects are directly emplaced into the workspace.

ROOT::TestSupport checks info/warning/error messages during unit tests.
Previously, it would generate one global failure irrespective of how
many messages have been received.
Now, each wrong message generates a dedicated failure.

- use TString method to check name for space symbol
- fix compiler warning

TRatioPlot defines three pads named upper_pad, lower_pad and top_pad.
If single canvas contains two or more TRatioPlots, the saved C macro
declares same object variable names resulting in runtime error. This
fix add counter suffix to pads (like for histograms) resulting in
unique pad names.

After my previous work on the RooFit minimizer interfaces, it is
relatively easy to allow passing a custom gradient function to the
RooMinimizer constructor.

The interface might still evolve in the future, but this commit is still
a milestone because now we can get actual `RooFitResult` objects that
were obtained minimizing a RooFuncWrapper that wraps both the likelihood
and the gradient code.

Some helper functionality that was originally in the new RooFuncWrapper
class but that is not needed anymore with the new minimizer interface
was removed.

C++20 is currently still known broken.

This reverts commit a4c07502.

While this itself might not cause build issues, the related commit 90ffa89a does;
handle them together.

This reverts commit 90ffa89a.
It causes build failures on GCC 12.2.1 / c++17 with

```
[ 70%] Generating G__Core.cxx, ../lib/Core.pcm
In file included from input_line_7:111:
/home/linev/build/webgui/include/ROOT/RDirectoryEntry.hxx:31:33: error: missing '#include <bits/chrono.h>'; 'system_clock' must be declared before it is used
   using clock_t = std::chrono::system_clock;
                                ^
/usr/include/c++/12/bits/chrono.h:1110:12: note: declaration here is not visible
    struct system_clock
           ^
In module 'std' imported from input_line_1:1:
/usr/include/c++/12/bits/move.h:204:11: error: missing '#include <bits/chrono.h>'; 'time_point' must be defined before it is used
      _Tp __tmp = _GLIBCXX_MOVE(__a);
          ^
/home/linev/build/webgui/include/ROOT/RDirectoryEntry.hxx:89:4: note: in instantiation of function template specialization 'std::swap<std::chrono::time_point<std::chrono::system_clock, std::chrono::duration<long, std::ratio<1, 1000000000>>>>' requested here
   swap(fDate, other.fDate);
   ^
/usr/include/c++/12/bits/chrono.h:856:14: note: definition here is not reachable
      struct time_point
```

This fixes building ROOT (and installing the prerequisite python packages)
e.g. on Alma9.