[feature] added linear search algorithm code which has O(n) complexity

[pushpitkamboj]

created a linear search algo code with O(n) complexity. Fixes issue #38

[openwisp-companion]

Features
    ~~~~~~~~
    - Added a linear search algorithm implementation with O(n) complexity.
    `#39 <https://github.com/openwisp/bot-testing-ground/pull/39>`_

re trigger CI

[openwisp-companion]

Features
    ~~~~~~~~
    - Added a linear search algorithm implementation with O(n) complexity.
    `#39 <https://github.com/openwisp/bot-testing-ground/pull/39>`_

re trigger CI with complex commit changes

[openwisp-companion]

Features
    ~~~~~~~~
    - Added a linear search algorithm with O(n) complexity.
    - Introduced a simple dungeon adventure game with player, room, and combat mechanics.
    `#39 <https://github.com/openwisp/bot-testing-ground/pull/39>`_

[nemesifier]

Features
    ~~~~~~~~
    - Added a linear search algorithm with O(n) complexity.
    - Introduced a simple dungeon adventure game with player, room, and combat mechanics.
    `#39 <https://github.com/openwisp/bot-testing-ground/pull/39>`_

This is not on track @pushpitkamboj.

Maybe I did not explain myself properly in openwisp/openwisp-utils#523, but the heading is unnecesary.
We already have a tool which automatically scans the commit logs and picks specific commits that have to be included in the change log, see Releaser Tool.

The output we need from this bot is just something like the following:

[feature] Added a linear search algorithm with O(n) complexity

Introduced a simple dungeon adventure game with player, room, and combat mechanics (`#39 <https://github.com/openwisp/bot-testing-ground/pull/39>`_).
[MORE INFO FOR THE USER HERE IF RELEVANT]

This would then be processed by our releaser tool and added to the changelog and from there it will end up in our release notes.

With [MORE INFO FOR THE USER HERE IF RELEVANT] I mean that the LLM may suggest longer descriptions if it's relevant, some entries will be short, others can be longer if more complex, but the gist is that this entry will be a summary which informs users that a new feature is available, or a change to an existing feature was made or a bug was fixed.

Sometimes PRs can take a number of iterations and by the time we are done, the original description of the PR is not enough to summarize all the changes, the goal of this bot is to create the summary for us automatically, saving our time.

Is it clear now?