5098: refactor old code to use User.progress

Now that #7061 is done, all the old code should no longer use
User.begin_.../step_.../end_progress directly any more, preferring
the context manager instead.

git-svn-id: svn+ssh://svn.code.sf.net/p/gramps/code/trunk@23096 4ae1f11a-8b86-4847-b8af-ab372f36d1fd
Revert "5098: refactor code to use User.progress"

This reverts commit db9a64ef7da5f26c586452c1a84a96675991d9a4.

This was tested with "runtest.sh" only, but turns out things
are broken under GUI. I'll investigate on a private branch,
reverting meanwhile to unblock the affected plugins on trunk.

git-svn-id: svn+ssh://svn.code.sf.net/p/gramps/code/trunk@23099 4ae1f11a-8b86-4847-b8af-ab372f36d1fd
5098: refactor to use user.info and user.progress

git-svn-id: svn+ssh://svn.code.sf.net/p/gramps/code/trunk@23100 4ae1f11a-8b86-4847-b8af-ab372f36d1fd
5098: rename gui.user.User.progress to ._progress

it shadowed the gen.user.User.progress (the context manager),
breaking the ``with user.progress() ... as step:'' idiom!

git-svn-id: svn+ssh://svn.code.sf.net/p/gramps/code/trunk@23101 4ae1f11a-8b86-4847-b8af-ab372f36d1fd
Revert*2 "5098: refactor code to use User.progress

Revert*2 means re-apply :-)

git-svn-id: svn+ssh://svn.code.sf.net/p/gramps/code/trunk@23102 4ae1f11a-8b86-4847-b8af-ab372f36d1fd
7061: docstring update

git-svn-id: svn+ssh://svn.code.sf.net/p/gramps/code/trunk@23104 4ae1f11a-8b86-4847-b8af-ab372f36d1fd