Implement a User Profile Composed of Address and Contacts

Create three classes: Address, Contact, and UserProfile. A UserProfile should contain an Address instance and a list of Contact instances (composition, not inheritance). Implement a helper function build_user(first_name, last_name, address_tuple, contacts_list) that constructs and returns a UserProfile. Implement user_summary(user) that returns a single-line string containing the user's full name, a nicely formatted address, and the primary contact's value. Primary contact selection rules: - If one or more contacts have preferred=True, select the first preferred contact in the list. - If none are preferred but contacts exist, select the first contact in the list. - If there are no contacts, the primary contact is None. Address formatting rules: - Always include street and city. - Append "state zip" together if either state or zip is non-empty. If both are empty, omit that part. - Separate parts with commas. End the address part with a period before the Primary label. Return format example: "Jane Doe, 123 Main St, Springfield, IL 62704. Primary: jane@example.com" Follow composition principles: UserProfile should store Address and Contact objects, not raw tuples.

Use composition to model a user profile with an address and a list of contacts. Implement functions to build profiles and produce a concise user summary string that selects the primary contact correctly.

Do not use inheritance for Address/Contact (use composition). Do not print; return a string from user_summary. Keep classes and functions pure and deterministic.