ARN classes should understand whether they have region or account values

Some ARNs, like for S3 buckets, have neither region nor account in them. Others, like IAM resources, don't have region but do have account. The ARN subclasses should be aware of this and, I would say, both refuse to create incorrect ARNs, and throw errors when parsing incorrect ARNs.