API - Resolve potential issues using dateTime.Now in mappings

cc: @william-liebenberg @lukecookssw @jasontaylordev

In one of our Automapper mapping profiles, we are using DateTime.Now:

.ForMember(dst => dst.PointsThisYear, opt => opt.MapFrom(src => src.UserAchievements
                                                                                    .Where(ua => ua.AwardedAt.Year == DateTime.Now.Year)
                                                                                    .Sum(ua => ua.Achievement.Value)))

This can present some issues when testing the query that's dependent on this DTO.

Options:

• Inject IDateTime into the DTO ctor (will need an explicit default ctor and an attribute for serialization)
• Map these fields explicitly in the query (use Ignore() for these fields and make multiple database calls to get the additional data)
• Don't use ProjectTo and map the whole DTO manually
• ...?

Locate the AutoMapper profile containing the PointsThisYear mapping and the DTO or query that uses ProjectTo. Reproduce the testing problem, then compare the listed time-source, explicit-query, and manual-mapping options; done means one chosen approach is implemented and the dependent query can be tested deterministically.