chore!: rename Prototyping asmdef to Components

[0xFA11]

We are planning to use this asmdef scope for Unity-dependent netcode types/components such as NetworkTransform, NetworkAnimator which are often relying on MonoBehaviour, ScriptableObject etc.

[jeffreyrainy]

I personally like this much more. Prototyping can mean "unfinished stuff we're currently messing with". Component captures better what NetworkTransform, at the very lest, is.

[andrews-unity]

I mean one thing about prototyping that is implied is that it may not be something we keep. Where I feel component doesn't really reflect that. For example while yes we have a NetworkTransform now but its not in a complete state its in some sort of state of dev, same with NetworkAnimator or NetworkNavMeshAgent are these things we want to fully support at this moment? I thought that was the reason for having it in the prototype namespace.

[0xFA11]

@andrews-unity

I mean one thing about prototyping that is implied is that it may not be something we keep. Where I feel component doesn't really reflect that. For example while yes we have a NetworkTransform now but its not in a complete state its in some sort of state of dev, same with NetworkAnimator or NetworkNavMeshAgent are these things we want to fully support at this moment? I thought that was the reason for having it in the prototype namespace.

We already committed to NetworkTransform and NetworkAnimator component (Sam & Philipp worked on those). We didn't rework NetworkNavMeshAgent yet (that might be dropped or reworked in the future).

The idea behind this asmdef will stay the same and won't necessarily change over time. We called it "Prototyping" initially because we didn't know what we were going to do but now we have a better understanding and plan about where to put Unity-oriented bespoke network components, this is what it looks like.

[mattwalsh-unity]

Does having this namespace buy us anything? I like moving things out of the Prototyping folder. But like, we have a number of things that are in folders (e.g. NetworkVariable) that are not in a NetworkVariable different namespace.

[0xFA11]

I'm going to inline some parts of our Slack conversation here too:

I think the difference is NetworkTransform, NetworkAnimator etc are going to be bespoke Unity-tailored components
Components is more like "bespoke network components to use in Unity world"
So, I wouldn't say NetworkVariable will be kicked out of Runtime/Core in the future, we'll probably keep it in the core long term