Fix calling ZeroMemset in deep_copy

[masterleinad]

While working on #5035, I realized that we don't call ZeroMemset in deep_copy as intended because std::is_trivially_copy_assignable<>::value is false for const types.

[dalg24]

BTW weren't we supposed to have kokkostool-based unit test for this?

[masterleinad]

BTW weren't we supposed to have kokkostool-based unit test for this?

We have one for View initialization but that doesn't cover deep_copy.

[dalg24]

Should we start using SKIP instead? (Not asking to change)

[masterleinad]

Retest this please,

[masterleinad]

Retest this please.

[dalg24]

Retest this please

[dalg24]

Any idea why GH workflow nor appveyor ran?

[masterleinad]

Any idea why GH workflow nor appveyor ran?

They ran for 1bc763d.
[ci skip] also works for GitHub Workflows, see https://docs.github.com/en/actions/managing-workflow-runs/skipping-workflow-runs, and appveyor, see https://www.appveyor.com/docs/how-to/filtering-commits/#skip-commits.