avoid property name conflicts in tests

[faustbrian]

1️⃣ Is this something that is wanted/needed? Did you create a feature-request issue first?
Yes. Fixes #381.

2️⃣ Does it contain multiple, unrelated changes? Please separate the PRs out.
No.

3️⃣ Does it include tests if possible? (Not a deal-breaker, just a nice-to-have)
Yes.

4️⃣ Please include a thorough description of the feature/fix and reasons why it's useful.
Prefixes the randomly generated name property with component to avoid naming conflicts and false results in tests.

5️⃣ Thanks for contributing! 🙌

[faustbrian]

@calebporzio I think it would be a good idea to start to use a convention like componentProperty for internal things of Livewire to avoid naming conflicts with components since things like ID and name are not the only common names for properties.

Potential prefixes for internal properties could be component, internal or _ to avoid naming conflicts. Even better maybe would be to use an array that holds all state that belongs to Livewire and not the part that is implemented by developers that extend the base component. That way naming conflicts would be basically impossible and all things Livewire inside the component are isolated from the things a developer adds.

[calebporzio]

Thanks @faustbrian!

And yeah, you're totally right. A dedicated array, or _ prefixed props is probably the way to go. Thanks.

[lancepioch]

@all-contributors please add @faustbrian for test

[allcontributors]

@lancepioch

I've put up a pull request to add @faustbrian! 🎉