build(deps): update optuna requirement from <4.0.0,>=3.1.0 to >=3.1.0,<5.0.0

[dependabot]

Updates the requirements on optuna to permit the latest version.

Release notes

Sourced from optuna's releases.

v4.1.0

This is the release note of v4.1.0. Highlights of this release include:

• 🤖 AutoSampler: Automatic Selection of Optimization Algorithms
• 🚀 More scalable RDB Storage Backend
• 🧑‍💻 Five New Algorithms in OptunaHub (MO-CMA-ES, MOEA/D, etc.)
• 🐍 Support Python 3.13

The updated list of tested and supported Python releases is as follows:

• Optuna 4.1: supported by Python 3.8 - 3.13
• Optuna Integration 4.1: supported by Python 3.8 - 3.12
• Optuna Dashboard 0.17.0: supported by Python 3.8 - 3.13

Highlights

AutoSampler: Automatic Selection of Optimization Algorithms

AutoSampler automatically selects a sampler from those implemented in Optuna, depending on the situation. Using AutoSampler, as in the code example below, users can achieve optimization performance equal to or better than Optuna's default without being aware of which optimization algorithm to use.

$ pip install optunahub cmaes torch scipy

import optuna
import optunahub
auto_sampler_module = optunahub.load_module("samplers/auto_sampler")
study = optuna.create_study(sampler=auto_sampler_module.AutoSampler())

See the Medium blog post for details.

Enhanced RDB Storage Backend

This release incorporates comprehensive performance tuning on Optuna’s RDBStorage, leading to significant performance improvements. The table below shows the comparison results of execution times between versions 4.0 and 4.1.

# trials	v4.0.0	v4.1.0	Diff
1000	72.461 sec (±1.026)	59.706 sec (±1.216)	-17.60%
10000	1153.690 sec (±91.311)	664.830 sec (±9.951)	-42.37%
50000	12118.413 sec (±254.870)	4435.961 sec (±190.582)	-63.39%

For fair comparison, all experiments were repeated 10 times, and the mean execution time was compared. Additional detailed benchmark settings include the following:

• Objective Function: Each trial consists of 10 parameters and 10 user attributes
• Storage: MySQL 8.0 (with PyMySQL)
• Sampler: RandomSampler
• Execution Environment: Kubernetes Pod with 5 cpus and 8Gi RAM

... (truncated)

Commits

• f8e1e6d Merge pull request #5751 from c-bata/bump-up-to-v4.1.0
• 604d45e Bump the version up to v4.1.0
• d9327ca Merge pull request #5741 from porink0424/fix/introduce-upsert-in-set_trial_sy...
• 2af7c61 Resolve a small linting problem
• d834afb Merge pull request #5745 from y0z/feature/update-docs
• d44be32 Merge pull request #5744 from nzw0301/update-actions/upload-artifact
• 5d678de Merge upstream
• 4689713 Add link to the autosampler article
• 8b648e9 Update docs/source/reference/samplers/index.rst
• 3eadc92 Add information about AutoSampler to the docs.
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[fkiraly]

Seems unproblematic.