Generate scalar properties for primitive types

[protocool]

This introduces a "scalars" boolean template variable for both the Objective-C and the Swift templates.

When true, property declarations for non-optional attributes with hasScalarAttributeType will use the appropriate scalar type and, in the case of Objective-C, omit the generated *Value accessors.

Additionally (when scalars=false), generated NSNumber properties for hasScalarAttributeType attributes in the Swift template will only be optional when the attribute is optional, just as it is for Strings or NSDate etc (if that's contentious then let me know, I just don't know of a reason why NSNumber should be any different).

This change may go some way to easing the pain described in #219, but Swift *Value accessors are a separate issue that probably still needs to be addressed.

Compatibility: Core Data support for scalar properties appeared in iOS 5 and OS X 10.7, though my own testing is limited to iOS 8 and 10.10.

[jeffwatkins]

I’d really love to see this become part of the standard distribution.

[justin]

We are declaring pull request and issue 0 now that 1.3 is out. If this is still an issue you'd like to see address with 1.30 and going forward, please open a new issue so we can start a fresh discussion. Thank you!