Description

In bconsole, when you type a command multiple times in a row, all these entries are saved in the history and make previous command navigation annoying.
Example: you do run job=xxx <a lot of arguments> yes and want to monitor the stats of the job, so you start typing status storage every now and then to see how the job is behaving. Now you want to rerun the same job with the same run job=xxx <a lot of arguments> yes command, but it is buried behind multiple status storage commands, and you would have to either press the arrow button up as many times as you entered the status storage command, or have to do a search. This PR changes the behavior by making sure multiple same commands in a row are only saved once.

Please check

• Short description and the purpose of this PR is present above this paragraph
• Your name is present in the AUTHORS file (optional)

If you have any questions or problems, please give a comment in the PR.

Helpful documentation and best practices

• Git Workflow
• Automatic Sourcecode Formatting
• Check your commit messages

Checklist for the reviewer of the PR (will be processed by the Bareos team)

General

• PR name is meaningful
• Purpose of the PR is understood
• Separate commit for this PR in the CHANGELOG.md, PR number referenced is same
• Commit descriptions are understandable and well formatted
• If backport: add original PR number and target branch at top of this file: Backport of PR#000 to bareos-2x

Source code quality

• Source code changes are understandable
• Variable and function names are meaningful
• Code comments are correct (logically and spelling)
• Required documentation changes are present and part of the PR
• bareos-check-sources --since-merge does not report any problems
• git status should not report modifications in the source tree after building and testing