[JENKINS-74054] Extract inline script block in AbstractNameValueHeader/rowHeader.jelly

[shlomomdahan]

JENKINS-74054

• Original functionality was broken. The tooltip was not appearing when hovering over the build number.

  • This is addressed in Fix jQuery target element for tooltip to work correctly in AbstractNameValueHeader/rowHeader.jelly #156 for the inline script which is extracted in this PR.

• The tooltip is necessary because the card lacks space to display all the parameters if many are present.

Testing done

1. Create a pipeline similar to [JENKINS-73960] Extract event handlers in BuildCardExtension/buildCardTemplate.jelly #142
2. For the upstream project, add a few random parameters.
3. Go to the pipeline config settings and enable the below setting:
   
4. This will display parameters on the first card in the pipeline.
   

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[basil]

Original functionality was broken. The tooltip was not appearing when hovering over the build number.

In the latest released version? I can't tell which portion of this diff is fixing a bug, if any.

[shlomomdahan]

Original functionality was broken. The tooltip was not appearing when hovering over the build number.

In the latest released version? I can't tell which portion of this diff is fixing a bug, if any.

@basil Apologies for not specifying.

In the original released version, the jQuery snippet was looking for an element build-parameters-trigger-...

There was no such element in the DOM. I added this ID to the <div> with the 'title' class.

[basil]

In the original released version, the jQuery snippet was looking for an element build-parameters-trigger-...

Makes sense. Can we please split that bug fix into a separate PR so that this extraction is reviewable as an extraction and not two independent changes?

[shlomomdahan]

@basil

Sure just created #156 for the split.