Store location information for users, events and groups in AddressField

Moving this to the main Commons queue since we'll likely want to standardize on a single solution for storing location information.

Benefits to using Addressfield:
- It's actively maintained by Commerce Guys, so it's unlikely to go anywhere
- It's got healthy project usage (30k sites and increasing at a rate that's increasing)
- Complies with xNAL standard
- It's limited in scope (collecting international postal addresses).

Are there any alternative systems that folks feel we should use instead?

Addressfield was committed in #1743416: Add Addressfield, Date to Commons make file.

Let's proceed with this as the selection, though it's certainly early enough to revisit if anyone has specific objections.

Mariomaric correctly points out I was a little overzealous in closing this issue - We haven't achieved the goal in the title yet ;).

In my view, locative information for users seems like an optional user profile field that we should include, and we should include it by default with Commons Groups.

I changed title to be even more precise. :)

So, we will include location information in:

• http://drupal.org/project/commons_groups + http://drupal.org/project/commons_events - I suggest that we try to make it available only if group is location based i.e hide address field input form if Event/Group is virtual.
• http://drupal.org/project/commons_profile_base - make it optional field (probably as Bio field?)

Did I understand this correctly?

Should we fill separate feature requests in each module issue queue?

@jpontani: Great, than we can reuse that principle. :)

JFTR, I closed (as duplicate) #1074208: Add a location field to group and event content types @ GDO issue queue.