Make use of jest .toMatchSnapshot in library unit tests

[danielcaldas]

Describe the issue
Currently there are a lot of cases where it makes sense to use .toMatchSnapshot instead of .toEqual.

Expected
In tests such as this example of graph.builder.spec.js, replace usages of super verbose and gigantic toEqual for toMatchSnapshot.

Example:

expect(props).toEqual({
    ...that.node,
    className: "node",
    cursor: "pointer",
    cx: 1,
    cy: 2,
    dx: 15.5,
    fill: "red",
    fontSize: 12,
    fontWeight: "bold",
    fontColor: "black",
    id: "id",
    label: "id",
    onClickNode: undefined,
    onRightClickNode: undefined,
    onMouseOut: undefined,
    onMouseOverNode: undefined,
    opacity: 1,
    renderLabel: true,
    size: 200,
    stroke: "yellow",
    strokeWidth: 2,
    svg: "file.svg",
    type: "circle",
    viewGenerator: null,
    overrideGlobalViewGenerator: undefined,
});

Files that should be tackled

• graph.builder.spec.js
• graph.helper.spec.js

Feel free to look around for other use cases that might make sense.

[jaydinsweo]

I would like to take this issue 👍🏻

[danielcaldas]

Go for it @nguyenami 💪

[danielcaldas]

Closing this with #243