[feature] Add a print function

[pushpitkamboj]

No description provided.

[openwisp-companion]

### Commit Message and Test Failures

Hello @pushpitkamboj,
*(Analysis for commit 4009d42)*

### Commit Message Failure

*   **Explanation**: The `checkcommit` tool failed because the commit message does not follow the required format. Specifically, it indicates "No capital letter after prefix." This means the commit message likely started with a prefix (e.g., `[fix]`) but the title that followed was not capitalized.
*   **Remediation**: Ensure your commit message follows this format:
    ```
    [tag] Capitalized short title #<issue_number>

    <Detailed description of the changes.>

    Fixes #<issue_number>
    ```
    For example:
    ```
    [fix] Correctly format commit messages #123

    This commit updates the commit message to adhere to the project's
    standard format, ensuring the title is capitalized after the tag
    and includes a detailed description and a closing keyword.
    Fixes #123
    ```

### Test Failure

*   **Explanation**: A `ValueError: Something went terribly wrong` occurred during test execution in `test.py` on line 10. The provided logs indicate a simulated error, suggesting a problem within the test execution environment or the test script itself.
*   **Remediation**: The `ValueError` appears to be a simulated failure within the test script (`test.py`). To fix this, you should examine `test.py` and remove or correct the line that is causing this `ValueError`. If this is intended to be a test for error handling, ensure the test correctly asserts the expected exception. Based on the provided logs, the issue is on line 10 of `test.py`.

    **Example of how to fix a simulated error:**

    If `test.py` contains:
    ```python
    # ... other code ...
    def some_test_function(self):
        # ... other assertions ...
        raise ValueError("Something went terribly wrong") # This line causes the failure
        # ... other assertions ...
    ```

    You should modify it to either remove the `raise` statement if it's not intended, or properly handle it within the test:

    **Option 1: Remove the simulated error**
    ```python
    # ... other code ...
    def some_test_function(self):
        # ... other assertions ...
        # Removed the line that caused the ValueError
        # ... other assertions ...
    ```

    **Option 2: Test for the expected exception**
    ```python
    # ... other code ...
    def some_test_function(self):
        # ... other assertions ...
        with self.assertRaises(ValueError) as cm:
            # Code that is expected to raise ValueError
            # For example, calling a function that might raise it
            some_function_that_raises_error()
        self.assertEqual(str(cm.exception), "Something went terribly wrong")
        # ... other assertions ...
    ```

[openwisp-companion]

[feature] Added a `print_number` function to `pushpit/binary_search.py`.

`#84 <https://github.com/openwisp/bot-testing-ground/pull/84>`_