fix(#17033): tooltip render and alignment issues in scrolltop

[tbui17]

fixes #17033

The issue stems from inconsistent designation of the target element for offset calculations in alignment. User should now be able to use the directive as expected like so:

<div style="width: 250px; height: 200px; overflow: auto">
      <p>
          Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Vitae et leo duis ut diam. Ultricies mi quis hendrerit dolor magna eget est lorem. Amet consectetur adipiscing
          elit ut. Nam libero justo laoreet sit amet. Pharetra massa massa ultricies mi quis hendrerit dolor magna. Est ultricies integer quis auctor elit sed vulputate. Consequat ac felis donec et. Tellus orci ac auctor augue mauris. Semper
          feugiat nibh sed pulvinar proin gravida hendrerit lectus a. Tincidunt arcu non sodales neque sodales. Metus aliquam eleifend mi in nulla posuere sollicitudin aliquam ultrices. Sodales ut etiam sit amet nisl purus. Cursus sit amet
          dictum sit amet. Tristique senectus et netus et malesuada fames ac turpis egestas. Et tortor consequat id porta nibh venenatis cras sed. Diam maecenas ultricies mi eget mauris. Eget egestas purus viverra accumsan in nisl nisi.
          Suscipit adipiscing bibendum est ultricies integer. Mattis aliquam faucibus purus in massa tempor nec.
      </p>
      <p-scrollTop target="parent" [threshold]="100" pTooltip="bottom" tooltipPosition="bottom" />
</div>

Changes

• align{direction} and getHostOffset methods all consistently use activeElement

Remarks

• I wasn't sure if PrimeNG was still updating v18, I can backport to v18 if needed.
• I would be very interested in helping out with testing. Update Component Tests #16788 Introduce E2E for end user tests #16857 I saw a lot of type inconsistencies that contribute to many other issues related to Tooltip.

Defect Fixes

When submitting a PR, please also create an issue documenting the error and manually link to an issue.

Feature Requests

Due to company policy, we are unable to accept feature request PRs with significant changes as such cases has to be implemented by our team following our own processes.
Smaller scaled feature implementations such as adding a property to a component will be considered for merging.

[vercel]

Deployment failed with the following error:

Creating the Deployment Timed Out.