Don't insert frames when expanding ASM pseudo instructions if EXPAND_FRAMES is not set.

Closes #317800

See merge request !52

Delete the examples.

See merge request !53

Deprecate the XML API.

See merge request !54

Improve the code quality of FieldWriter.

See merge request !64

Add the signature files for ASM 6.0.

See merge request !49

Remove the duplicated signature files.

See merge request !51

Fix the order of the arguments when writing code attributes.

Closes #317796

See merge request !47

The signature test was not working without the rt.jar on the classpath (no error was reported for incompatible API changes). Adding it solves this issue, and also removes the warnings about the @Deprecated annotations. I also had to manually fix the asm-xml signature files (for some unknown reason the inner ASMContentHandler$Rule class was recorded as public, whereas it has always been protected).

These examples were introduced long before the user guide, which now provides more and better documented examples.

ASM pseudo instructions are used when jump instructions need to be resized in large methods. To convert them to normal instructions, a new ClassReader->ClassWriter roundtrip is performed, with the EXPAND_ASM_INSNS flag and with the EXPAND_FRAMES flag if the class already had frames (see ClassWriter#toByteArray). If EXPAND_FRAMES is false this means the class had initially no frames, despite the fact that it has jump instructions (otherwise there could not be any ASM pseudo insns to replace). Therefore, in this case, we should not attempt to insert frames in ClassReader.

This makes some tests fail due to issue #317800. This issue will be fixed in the next commit.

Some files differ from the content for the previous version only by the version number line, everything else being identical. They can be removed since they only give redundant tests and increase the build time for nothing.