After updating to 1.0.0 AtlasObjectId's no longer work

[Connie Chen]

Hi, after we upgraded from 0.8.1 to 1.0.0, using `AtlasObjectId` in the
`AtlasClientV2` no longer works, it gives this error

{\"errorCode\":\"ATLAS-400-00-021\",\"errorMessage\":\"ObjectId is not
> valid [{guid=68fb7501-63be-44c5-9e96-823314ee614a, typeName=schema}]\"})
> class java.lang.IllegalArgumentException"}


Here is a debug line from Atlas

21848 DEBUG org.apache.atlas.AtlasBaseClient  - Request      :
> AtlasEntityWithExtInfo{entity=AtlasEntity{AtlasStruct{typeName='s3',
> attributes=[schema:[AtlasObjectId{guid='68fb7501-63be-44c5-9e96-823314ee614a',
> typeName='schema', uniqueAttributes={}}], awsRegion:us-east-1 ....}


You can see that I am sending AtlasObjectId as before. I don't understand
why this is suddenly happening, I looked at the examples in QuickStartV2
and for references it is still constructing `AtlasObjectId` in the same way
with the guid and typeName, so why are my AtlasObjectId's now invalid?

Connie