Integrate filtering by node name across graphs with next/previous buttons about step49-2020 HOT 1 CLOSED

• User search for node X at graph index G-index
• X not in current graph
  • X not in mutations list --> display error message
  • X in mutations list
    • find next smallest mutation index after G-index (or prev greatest mutation index) M-index
    • jump graph to M-index.
    • next/prev should display the next/prev index in filteredMutationsIndices (mutation indices that only mutates the filtered node)
• X in current graph
  • G-index in filteredMutationsIndices
    • graph is already at G-index, and should stay at G-index
    • next/prev should display the next/prev index in filteredMutationsIndices
  • G-index 2 not in filteredMutationsIndices [1, 3, 5]
    • Option 1: insert G-index into filteredMutationsIndices
      - why still display G-index - kind of weird
    • [x]Option 2: keep filteredMutationsIndices the same, but still display G-index. Next/Prev would never return to G-index
      - what about "Displaying ??? out of 3 (this is 2 on the original)"?
      - Display some other message, e.g. this graph is not in the list of relevant mutations
      - Just display "this is G-index on the original", don't display relative index.
      - Client-side logic to figure out what "next" and "prev" mutation indexes should be

from step49-2020.