Change build logic so that the VM prefix on a class name does not control inclusion in the bootimage

Historically the VM* name meant bootimage inclusion. We've partially moved away from that, but there are still a few remnants. Get rid of them while maintaining approximately the same set of classes included in the bootimage.

With the change I'm testing now, the only significant difference is that a bunch of opt-compiler specific classes from ArchitectureSpecific get sucked into bootimage that don't include the opt compiler. This isn't ideal, but I think we can live with it for now. As we reduce usage of ArchitectureSpecific in the opt compiler (which we really should be doing anyways), this will go away. For the record, the list of classes is:

> Lorg/jikesrvm/ArchitectureSpecific;
> Lorg/jikesrvm/ArchitectureSpecific$Assembler;
> Lorg/jikesrvm/ArchitectureSpecific$BURS_Debug;
> Lorg/jikesrvm/ArchitectureSpecific$BURS_STATE;
> Lorg/jikesrvm/ArchitectureSpecific$BURS_TreeNode;
> Lorg/jikesrvm/ArchitectureSpecific$CallingConvention;
> Lorg/jikesrvm/ArchitectureSpecific$ComplexLIR2MIRExpansion;
> Lorg/jikesrvm/ArchitectureSpecific$ConvertALUOperators;
> Lorg/jikesrvm/ArchitectureSpecific$FinalMIRExpansion;
> Lorg/jikesrvm/ArchitectureSpecific$GenerateMachineSpecificMagic;
> Lorg/jikesrvm/ArchitectureSpecific$MIROptimizationPlanner;
> Lorg/jikesrvm/ArchitectureSpecific$NormalizeConstants;
> Lorg/jikesrvm/ArchitectureSpecific$PhysicalDefUse;
> Lorg/jikesrvm/ArchitectureSpecific$PhysicalRegisterConstants;
> Lorg/jikesrvm/ArchitectureSpecific$PhysicalRegisterSet;
> Lorg/jikesrvm/ArchitectureSpecific$PhysicalRegisterTools;
> Lorg/jikesrvm/ArchitectureSpecific$RegisterPool;
> Lorg/jikesrvm/ArchitectureSpecific$RegisterPreferences;
> Lorg/jikesrvm/ArchitectureSpecific$RegisterRestrictions;
> Lorg/jikesrvm/ArchitectureSpecific$StackManager;