feat: Refactor object spawn and unspawn logic

[MS-crew]

Description

Describe the changes

What is the current behavior? (You can also link to an open issue here)

What is the new behavior? (if this is a feature change)

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Other information:

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentations

Submission checklist

• I have checked the project can be compiled
• I have tested my changes and it worked as expected

Patches (if there are any changes related to Harmony patches)

• I have checked no IL patching errors in the console

Other

• Still requires more testing

[Someone-193]

I mean, this makes sense to me, but we're 100% sure there's no reason it's the old way specifically right?

[VALERA771]

I mean, this makes sense to me, but we're 100% sure there's no reason it's the old way specifically right?

I was also thinking about this. I assume there must be a reason why we don't use NetworkServer methods for this. I think we don't have a choice, we need to do some tests

[MS-crew]

I mean, this makes sense to me, but we're 100% sure there's no reason it's the old way specifically right?

I was also thinking about this. I assume there must be a reason why we don't use NetworkServer methods for this. I think we don't have a choice, we need to do some tests

simply because the old writer didn't know these methods and made a mistake