N°7939 - Improve activity panel tab togglers when there's more than 2 log attributes

[steffunky]

Base information

Question	Answer
Related to a SourceForge thead / Another PR / Combodo ticket?	N°7939
Type of change?	Bug fix

Symptom (bug)

When there's more than 2 attribute log in a class, the display is broken

Reproduction procedure (bug)

Add more caselog attribute to a class, open the activity panel

    <class id="UserRequest">
      <fields>
        <field id="public_log2" xsi:type="AttributeCaseLog" _delta="define">
          <sql>public_log2</sql>
          <default_value/>
          <is_null_allowed>true</is_null_allowed>
        </field>
        <field id="public_log3" xsi:type="AttributeCaseLog" _delta="define">
          <sql>public_log3</sql>
          <default_value/>
          <is_null_allowed>true</is_null_allowed>
        </field>
        <field id="public_log4" xsi:type="AttributeCaseLog" _delta="define">
          <sql>public_log4</sql>
          <default_value/>
          <is_null_allowed>true</is_null_allowed>
        </field>
        <field id="public_log5" xsi:type="AttributeCaseLog" _delta="define">
          <sql>public_log5</sql>
          <default_value/>
          <is_null_allowed>true</is_null_allowed>
        </field>
      </fields>
      <presentation>
        <details>
          <items>
            <item id="public_log2" _delta="define">
              <rank>55</rank>
            </item>
            <item id="public_log3" _delta="define">
              <rank>56</rank>
            </item>
            <item id="public_log4" _delta="define">
              <rank>57</rank>
            </item>
            <item id="public_log5" _delta="define">
              <rank>58</rank>
            </item>
          </items>
        </details>
      </presentation>
    </class>

Proposed solution (bug and enhancement)

This PR adds a scroll to the tab toggler toolbar. It also makes sure that if a caselog tab is specified in the url, the toolbar is scrolled so that the current tab toggler is visible

Checklist before requesting a review

• I have performed a self-review of my code
• I have tested all changes I made on an iTop instance
• I have added a unit test, otherwise I have explained why I couldn't
• Is the PR clear and detailed enough so anyone can understand digging in the code?