Update libraries and python 3.11

[Martin-Molinero]

Description

• Update libraries and python 3.11

Related Issue

Closes #7663 Python update

Closes #7560
Closes #7606
Closes #7619
Closes #7623
Closes #7629
Closes #7631
Closes #7636
Closes #7665
Closes #7694
Closes #7711
Closes #7721
Closes #7776
Closes #7779
Closes #7780 mlfinlab no longer supported
Closes #7800 skipped because supports py <= 3.8. sktime/pytorch-forecasting#1301
Closes #7807
Closes #7810 works with keras < 3 philipperemy/keras-tcn#256
Closes #7851

Removing
FinRL doesn't support py 3.11 ref AI4Finance-Foundation/FinRL#1063
mxnet (read only repo) using Graphviz version from 2018 apache/mxnet#20897
pykalman failing, last update 9 year ago https://github.com/pykalman/pykalman
tigramite depends on numba 0.56.4 that doesn't work in py 3.11 jakobrunge/tigramite#400
tick doesn't support py 3.11 X-DataInitiative/tick#521
fracdiff Readonly/archived repo fracdiff/fracdiff#174 & fracdiff/fracdiff#153
dv supports old pandas/pydantic/SQLAlchemy, last update 3 years ago nteract/dx#28
ppscore requires old pandas, last update 2 years ago 8080labs/ppscore#76

Moving
scikeras since requires keras < 3 adriangb/scikeras#315
autokeras since requires keras < 3 keras-team/autokeras#1906
tensorflow-ranking not working with latest TF (will use TF 2.14.1) tensorflow/ranking#362
tensorflow-addons not working with latest TF (will use TF 2.14.1) (is shutting down) tensorflow/addons#2807
nixtlats depends on pydantic<2 Nixtla/nixtla#228
pearl depends on importlib-metadata<5.0.0 pearl-core/pearl#125

Motivation and Context

N/A

Requires Documentation Change

N/A

How Has This Been Tested?

Existing and new tests

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• Refactor (non-breaking change which improves implementation)
• Performance (non-breaking change which improves performance. Please add associated performance test and results)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Non-functional change (xml comments/documentation/etc)

Checklist:

• My code follows the code style of this project.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>