[KED-2099] Use the same JSON mock data files for JS+Python end unit/e2e tests

[studioswong]

Description

This PR aims to create a common test dataset that will be used in tests on both the Kedro-viz and Kedro-core projects.

Development notes

The following are introduced in this PR:

1. Set up of the dataset (test-data.json) to replace the original data set (animals.mock.js) that was used throughout the tests for the FE.The dataset is based on the animals dataset, with the only difference in the id field under nodes, as well as the edges field in hash data format instead of string format. This is needed to allow the same dataset to be used by the Kedro-core tests.

The same data set has also been passed to Kiyo to test with the BE and could be subjected to revisions.

2. Update mockState to reference the test-data.json file in constructing the mock data.

3. Update of all tests to replace the usage of the animals dataset to use the new test-data dataset.

4. Revision of existing tests that references and tests with the id field of nodes to use hash data rather than the string data as setup previously.

I have still kept the animals dataset given it is still used as a sample data set under data-source.js. I have also kept the reference to the animals dataset within data-source.js and its relevant test.

I have also kept the documentation as is with the reference to the animals dataset - @richardwestenra please let me know your thoughts, and we could revert to replacing the animals dataset entirely with the test-data dataset and I could make the relevant changes in data-source.js and the contribution docs.

Many thanks to @921kiyo and @richardwestenra for your help and collaboration on this ticket!

QA notes

N/A

Checklist

• Read the contributing guidelines
• Opened this PR as a 'Draft Pull Request' if it is work-in-progress
• Updated the documentation to reflect the code changes
• Added new entries to the RELEASE.md file
• Added tests to cover my changes

Legal notice

• I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

• I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.

• I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorised to submit this contribution on behalf of the original creator(s) or their licensees.

• I certify that the use of this contribution as authorised by the Apache 2.0 license does not violate the intellectual property rights of anyone else.

[richardwestenra]

@studioswong Pro tip: Instead of adding "WIP" to the PR title, you can open a draft pull request instead!

[studioswong]

@studioswong Pro tip: Instead of adding "WIP" to the PR title, you can open a draft pull request instead!

Thanks for the pro tip Richard 👍 ! Yea I originally thought of opening this as a draft PR as well, but on second thought I think it might be more straight forward to just set this up as an actual PR so we can just merge this in directly on obtaining confirmation from Kiyo with the test data file on their side - my attempts to avoid another PR :D ( The WIP is indicative that I might push new changes for the test data file)

Sorry I should've mentioned this in my description! I can also close this and open another draft one if this turns out to be more more upcoming changes than intended ;)

[921kiyo]

I've just removed input.json in #281, and started using animal test data, so you can delete this file :)

[studioswong]

awesome, thanks Kiyo!

[richardwestenra]

Nice work! A couple of notes, that I'm happy to pair with you and discuss if you like

[studioswong]

As @richardwestenra and I discussed, I will construct a separate PR for changing demo.mock.js into a json file and updating relevant tests after this PR is merged.