remove redundant methods in RichProgressBar

[quancs]

What does this PR do?

after #10896 _init_progress should run in the spawned processes already. We can remove this setstate method entirely.
see #10875 (comment)

Does your PR introduce any breaking changes? If yes, please list them.

Before submitting

• Was this discussed/approved via a GitHub issue? (not for typos and docs)
• Did you read the contributor guideline, Pull Request section?
• Did you make sure your PR does only one thing, instead of bundling different changes together?
• Did you make sure to update the documentation with your changes? (if necessary)
• Did you write any new necessary tests? (not for typos and docs)
• Did you verify new and existing tests pass locally with your changes?
• Did you list all the breaking changes introduced by this pull request?
• Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review

Anyone in the community is welcome to review the PR.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

• Is this pull request ready for review? (if not, please submit in draft mode)
• Check that all items from Before submitting are resolved
• Make sure the title is self-explanatory and the description concisely explains the PR
• Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?

Make sure you had fun coding 🙃

[awaelchli]

This PR does not address the comment you are linking to. There must be a misunderstanding. Two scenarios:

1. Either the Console object is pickleable and you can construct it on the main process, pass it in to the callback,
2. Or, the Console object is not pickleble, hence we only store the kwargs and make sure we construct it only in the worker process

Only one of the two applies, and given the existing code I suspect 2 is the case.

[quancs]

This PR does not address the comment you are linking to. There must be a misunderstanding. Two scenarios:

1. Either the Console object is pickleable and you can construct it on the main process, pass it in to the callback,

2. Or, the Console object is not pickleble, hence we only store the kwargs and make sure we construct it only in the worker process

Only one of the two applies, and given the existing code I suspect 2 is the case.

OK, then what should I do in this PR

[awaelchli]

I believe just removing this code:

    def __getstate__(self):
        # can't pickle the rich progress objects
        state = self.__dict__.copy()
        state["progress"] = None
        state["_console"] = None
        return state
    def __setstate__(self, state):
        self.__dict__ = state
        self._console = Console(**self._console_kwargs)

[quancs]

@awaelchli removed.

[tchaton]

LGTM !