This removes WasmTagType. WasmTagType contained an attribute and a
signature index:
struct WasmTagType { uint8_t Attribute; uint32_t SigIndex; };
Currently the attribute field is not used and reserved for future use,
and always 0. And that this class contains SigIndex as its property is
a little weird in the place, because the tag type's signature index is
not an inherent property of a tag but rather a reference to another
section that changes after linking. This makes tag handling in the
linker also weird that tag-related methods are taking both WasmTagType
and WasmSignature
even though WasmTagType contains a signature
index. This is because the signature index changes in linking so it
doesn't have any info at this point. This instead moves SigIndex to
struct WasmTag itself, as we did for struct WasmFunction in D111104.
In this CL, in lib/MC and lib/Object, this now treats tag types in the
same way as function types. Also in YAML, this removes struct Tag,
because now it only contains the tag index. Also tags set SigIndex in
WasmImport's union, as functions do.
I think this makes things simpler and makes tag handling more in line
with function handling. These two shares similar properties in that both
of them have signatures, but they are kind of nominal so having the same
signature doesn't mean they are the same element.
Also a drive-by fix: the reserved 'attirubute' part's encoding changed
from uleb32 to uint8 a while ago. This was fixed in lib/MC and
lib/Object but not in YAML. This doesn't change object files because the
field's value is always 0 and its encoding is the same for the both
encoding.
This is effectively NFC; I didn't mark it as such just because it
changed YAML test results.
Why have a separate tagTypes() method? Wouldn't be better just add Type o Sig to struct WasmTag?