Exclude additional components from testSerializeOpenSimObjects that cause sporadic failure

[nickbianco]

Brief summary of changes

Self explanatory.

Testing I've completed

Ran testSerializeOpenSimObjects locally until sporadic failures stopped occuring.

Looking for feedback on...

CHANGELOG.md (choose one)

• no need to update because...internal fix.

---

This change is 

[carmichaelong]

PR Looks good to me as is, so I'm approving. Thanks for carefully combing through those intermittent issues.

Some ideas (could be a separate PR):

• Seems like for at least one these objects, the issue is even applying a random set of values. Would it be fair to keep trying random sets until a valid one is reached?
• More broadly, for the purpose of this test, is randomization necessary (or just a stronger conditions)? If not, should we assign specific values that work and it'll still test the serialization/deserialization steps?

@carmichaelong reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @nickbianco)

[nickbianco]

Thanks @carmichaelong. I've opened #4137 to capture the larger issue with this test.