The result numbers can be incorrect when there are more than one test with the same name

[ILer32]

Problem
When there are more than one test with the same name,

1. the results (test, failed test, asserts, passed, failed) can be incorrect.
2. the formatting of the warning messages can be improved.

For example

#include <boost/ut.hpp>
    
int main(int argc, const char* argv[]) {
    using namespace boost::ut;

    "test 1"_test = [] {
        expect(1 == 1_i);
        expect(2 != 2_i); //false
    };
    "test 1"_test = [] {
        expect(3 == 3_i);
    };
}

Expected Behavior

UT starts =====================================================================
Running test "test 1"...
FAILED in: C:\Users\CIL\Desktop\Test folder\BoostUtTest\example.cpp:8 - test condition: [2 != 2]
===============================================================================
Suite global
tests:   2 | 1 failed
asserts: 3 | 2 passed | 1 failed
Completed =====================================================================

Actual Behavior

UT starts =====================================================================
Running test "test 1"...
FAILED in: ...\example.cpp:8 - test condition: [2 != 2]WARNING test 'test 1' for test suite 'global' already present

Running test "test 1"...
===============================================================================
Suite global
tests:   2 | 2 failed
asserts: 5 | 3 passed | 2 failed
Completed =====================================================================

[ILer32]

Hi @kris-jusiak,
For users, same key name may be applied in the same layer.
For example,

#include <boost/ut.hpp>
int main() {
    ....
    "Scenario"_test = [] {
        given("I have...") = [] {
            when("I run...") = [] {
                then("Do A") = [] { .... };
                then("Do A again") = [] { .... };
                then("Do A again") = [] { .... };
                ....
            };
        };
    };
}

Warning messages for the same test name may not be a good solution.
Introducing a new field, test_id, as follows to distinguish different elements can be a solution.

  struct test_result {
    ....
    std::size_t test_id = 0LU;
    /*std::unique_ptr<map<std::string, test_result>> nested_tests =
        std::make_unique<map<std::string, test_result>>();*/
    std::vector<...> children;
  };

However, during addressing the issue, there are many optimization can be applied.
I am not the owner of this project. I do not know which part of the project can be or can not be changed.
Do you prefer to address the issue by yourself or let me try it first?

[kris-jusiak]

@ILer32 Feel free to tackle any issues you see and thank you for your valubale contributions

[ILer32]

The issue is solved.