Nightingale upgrade

[dlrice]

Notes

• Apologies but this PR includes changes from the tooltip PR which as already been approved. Somehow I can't disregard those changes here.
• Some delay on the MSA loading in alignment overview. I will continue to look at this as I assume the change will want to be made in the nightingale codebase.

Purpose

Upgrade to the latest nightingale v5

Approach

• Upgrade protvista packages to the latest nightingale
  • Feature.accession now acts as the protvista feature ID
  • displaystart --> display-start / displayend --> display-end
• Replace protvista-datatable with new React component TableFromData.
  • This has the consumer provide a column configuration similar to our results tables.
  • Table rows which are in range or are active are now managed using props markBackground and markBorder
• Incorporate tooltips everywhere using the new tooltip.ts functions which are based on floating-ui.
• Update to latest protvista-uniprot and adapt filtering logic
• Saw repeated attempts to reregister nightingale components so adapted the global customElements.define to make sure this doesn't happen. I did spend some time trying to figure out why this was happening but couldn't find the source.

Follow on tasks

• Extract 3D structures table from protvista-uniprot into uniprot website
• useDeferredValue for nightingale + table interaction
• Reimplement filter-scroll

Testing

Added and updated.

Checklist

• My PR is scoped properly, and “does one thing only”
• I have reviewed my own code
• I have checked that linting checks pass and type safety is respected
• I have checked that tests pass and coverage has at least improved, and if not explained the reasons why

[dlrice]

This seems duplicated by L183?

[Swaathik]

that' right. There is no need for two separate functions. hideTooltip is complete. Do you have any suggestion for a name of the event handler?