Allow filtering through next and previous buttons

[haoyxc]

Allows user to see only mutations relevant to a searched node

• Return a list of the relevant mutation indices to the client rather than just the mutation number
• Allow the user to search for a node, and respect the radius of the search
• Display the number of applicable mutations on the page as well as its position in the overall mutation list
• Created a map from nodeName -> mutation indices for caching
• Add a pop of (bright) color to the searched node
• Added tests to the new functions
• If the user is at an unfiltered graph and filters the graph, then if 1) the node is in the graph, it'll just be a generic search. if 2) the node is not on the graph, the user will see that and have the option to continue clicking forward. It will be graphs that are after the current graph their on. gotta love time series

Video: DNE.zip (the mutation file I have isn't updated, so sometimes the clicks don't generate a viewable mutation. it's because sometimes there's stuff like in my mutation file)

This PR doesn’t address the entirety of the “Integrate filtering by node name across graphs with next/previous buttons” issue. What's left is integrating with mutation reasoning/highlighting

Things to consider If user searches for a node and then clears, what graph should they be brought to? (the initial one, or the same one they’re currently on with all the nodes?) The current implementation is that if the filter changes, the graph will be the same. Just with different nodes.

note: please let me know any issues! I really wanted some feedback on implementation!

[google-cla[bot]]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to determine that you authored the commits in this PR. Maybe you used a different email address in the git commits than was used to sign the CLA? If someone else authored these commits, then please add them to this pull request and have them confirm that they're okay with them being contributed to Google. If there are co-authors, make sure they're formatted properly.

In order to pass this check, please resolve this problem and then comment@googlebot I fixed it... If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[google-cla[bot]]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to determine that you authored the commits in this PR. Maybe you used a different email address in the git commits than was used to sign the CLA? If someone else authored these commits, then please add them to this pull request and have them confirm that they're okay with them being contributed to Google. If there are co-authors, make sure they're formatted properly.

In order to pass this check, please resolve this problem and then comment@googlebot I fixed it... If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[IshaniSanturkar]

Not done reviewing completely, I'll take some time to understand the code more!

[google-cla[bot]]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to determine that you authored the commits in this PR. Maybe you used a different email address in the git commits than was used to sign the CLA? If someone else authored these commits, then please add them to this pull request and have them confirm that they're okay with them being contributed to Google. If there are co-authors, make sure they're formatted properly.

In order to pass this check, please resolve this problem and then comment@googlebot I fixed it... If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[google-cla[bot]]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to determine that you authored the commits in this PR. Maybe you used a different email address in the git commits than was used to sign the CLA? If someone else authored these commits, then please add them to this pull request and have them confirm that they're okay with them being contributed to Google. If there are co-authors, make sure they're formatted properly.

In order to pass this check, please resolve this problem and then comment@googlebot I fixed it... If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[google-cla[bot]]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to determine that you authored the commits in this PR. Maybe you used a different email address in the git commits than was used to sign the CLA? If someone else authored these commits, then please add them to this pull request and have them confirm that they're okay with them being contributed to Google. If there are co-authors, make sure they're formatted properly.

In order to pass this check, please resolve this problem and then comment@googlebot I fixed it... If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.