Update smoke test for atree inlining

[fxamacker]

Closes #343
Updates epics #292
Updates #296 #297

This PR updates smoke test to test mutation of child container:

• existing child retrieved from parent array/map
• new child appened/inserted to parent array
• existing child set in parent array/map
• new child set in parent map

This PR also added flag -slabcheck to enable in-memory slab validation and slab serialization validation. This check is time-consuming so it is disabled by default.

While at it, also refactored smoke tests.

---

• Targeted PR against main branch
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work
• Code follows the standards mentioned here
• Updated relevant documentation
• Re-reviewed Files changed in the Github PR explorer
• Added appropriate labels

[codecov-commenter]

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (0fc8f74) 62.58% compared to head (25dbc3e) 62.58%.

Additional details and impacted files

@@                     Coverage Diff                     @@
##           feature/array-map-inlining     #348   +/-   ##
===========================================================
  Coverage                       62.58%   62.58%           
===========================================================
  Files                              15       15           
  Lines                           10559    10559           
===========================================================
  Hits                             6608     6608           
  Misses                           3008     3008           
  Partials                          943      943           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[turbolent]

Great work!

I mostly focused on the Go code itself, I'm not too familiar with the original version of the stress testing

[turbolent]

Is there a chance that his becomes negative?

[fxamacker]

No, because new element is appended to expectedValues in the same code block so expectedValues has at least one element.

atree/cmd/stress/array.go

Lines 328 to 344 in 25dbc3e

	// Update expectedValues
	expectedValues = append(expectedValues, expectedChildValue)
	// Update array
	err = array.Append(child)
	if err != nil {
	return nil, 0, fmt.Errorf("failed to append %s: %s", child, err)
	}
	if nextOp == arrayMutateChildContainerAfterAppend {
	index := len(expectedValues) - 1
	expectedValues[index], err = modifyContainer(expectedValues[index], child, nextNestedLevels)
	if err != nil {
	return nil, 0, fmt.Errorf("failed to modify child container at index %d: %w", index, err)
	}
	}

[turbolent]

Nit: This looked like a single value to me at first when reading the changes above. Maybe switch the order to "value array"?

[fxamacker]

Actually, arrayValue is a single atree.Value, which happens to use Go array under the hood.

I added this comment to clarify:

// arrayValue is an atree.Value that represents an array of atree.Value.
// It's used to test elements of atree.Array.
type arrayValue []atree.Value