[HPO] update to sigopt new experiment api
* follow https://docs.sigopt.com/experiments

Signed-off-by: Wang, Yi A <yi.a.wang@intel.com>

# What does this PR do?

<!--
Congratulations! You've made it this far! You're not quite done yet though.

Once merged, your PR is going to appear in the release notes with the title you set, so make sure it's a great title that fully reflects the extent of your awesome contribution.

Then, please replace this with a description of the change and which issue is fixed (if applicable). Please also include relevant motivation and context. List any dependencies (if any) that are required for this change.

Once you're done, someone will review your PR shortly (see the section "Who can review?" below to tag some potential reviewers). They may suggest changes to make the code even better. If no one reviewed your PR after a week has passed, don't hesitate to post a new comment @-mentioning the same persons---sometimes notifications get lost.
-->

<!-- Remove if not applicable -->

Fixes https://github.com/huggingface/transformers/issues/18145


## Before submitting
- [ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
- [x] Did you read the [contributor guideline](https://github.com/huggingface/transformers/blob/main/CONTRIBUTING.md#start-contributing-pull-requests),
      Pull Request section?
- [ ] Was this discussed/approved via a Github issue or the [forum](https://discuss.huggingface.co/)? Please add a link
      to it if that's the case.
- [ ] Did you make sure to update the documentation with your changes? Here are the
      [documentation guidelines](https://github.com/huggingface/transformers/tree/main/docs), and
      [here are tips on formatting docstrings](https://github.com/huggingface/transformers/tree/main/docs#writing-source-documentation).
- [ ] Did you write any new necessary tests?


## Who can review?

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

trainer: @sgugger

@kding1 @yao-matrix @sgugger please have a review<|||||>_The documentation is not available anymore as the PR was closed or merged._<|||||>Hi @sywangyi, thanks for your contribution 🤗.

The current changes introduce a significant breaking change and we tend to limit them as much as possible.
Still, we though about this and we would like to propose 3 options in order to keep backward compatibility with previous sigopt versions:

1. Introduce a `if sigopt_version < x.y.z` -> previous behaviour `else` -> new behaviour in this PR
2. Split the current implement and the one introduced in this PR in two distinct functions and dispatch to the right one based on the sigopt version
3. Keep only the behaviour introduced in this PR but guard with a version check, raising an error if the version is too old to inform the user to upgrade its dependency.

Please pick one of the suggested options above (_or comment with potential other alternatives 🤓_) and we will be on track for merging 🤗.

Thanks, 
Morgan<|||||>@mfuntowicz hi, thanks for the suggestion, and choose option 1 and patch is uploaded<|||||>Thanks a lot @sywangyi!

It looks good to me, the failure in the CI seems related but I will let @sgugger have the final word 😃 