more consistent behavior with for setAttribute

I can specify strings instead of AttributeKey objects in the concrete5 core, let's do the same for "Data"