feat: Introduce ComponentPackage and ComponentTemplate

[igamigo]

Part of #550.
Introduces a first draft of ComponentPackage and ComponentTemplate.

For now it can serialize and deserialize configs such as this one:

name = "Test Component"
description = "This is a test component"
version = "1.0.0"
targets = ["FungibleFaucet"]

[[storage]]
name = "slot0"
description = "First slot"
slot = 0
value = "0x2551340000000000af02000000000000a3db000000000000ffeeff0f00000000"

[[storage]]
name = "multi"
description = "Multi slot entry"
slots = [1, 2, 3]
values = [["3428645", "687", "0xdba3", "0xfffeeff"], "0x2551340000000000af02000000000000a3db000000000000ffeeff0f00000000", "0x2551340000000000af02000000000000a3db000000000000ffeeff0f00000000"]

Most structs down to the element need to have custom (de)serialization due to the different alternatives discussed in #550, but at least now it's easy if we want to add a new away of encoding things such as felts (for instance, if we want to allow for binary representation for elements).

Planned follow-ups:

• Finish storage maps (this PR just includes scaffolding for it)
• Finish template matching ({{foo.bar.baz}}) for matching whole words or single elements

[bobbinth]

Looks good! Thank you! I left just a few comments inline.

[bobbinth]

Should this point be about storage maps?

[bobbinth]

Should this be just Word? I guess the question is whether it makes sense to keep the original representation at this level as well. The alternative would be to convert WordRepresentation to Word when we go from RawStorageEntry to StorageEntry.

[igamigo]

I debated this as well. I think the only real upside of keeping the representation is to be able to get the original representation when unpacking or inspecting packages. Whether this is valuable, I'm not sure. I think whether the value is defined as elements or as a binary number, for instance, could sometimes give some more semantic context to the entry itself, but obviously not sure it will be very useful versus just parsing as words and keeping that (probably less error prone as well, though this is easily tested).
I was thinking of adding some methods for more simply retrieving Word from each entry while keeping the original representation, but again maybe this is too much.

[bobbinth]

nit: I'm not 100% sure about the naming here. I think of this data more like "metadata" rather than config or template.

[igamigo]

Renamed to ComponentMetadata