Design an automation solution for Membership naming along the lines of NPSP Opportunity naming

[davidmreed]

ACs:

• Ability to specify any field from the Membership object, or any static value, or combination thereof to specify a Name field.
• Use merge syntax that is as close to NPSP's Opportunity naming syntax as possible.
• Build parsing and merging code (possibly copied from NPSP) to support this functionality in an Apex trigger.

[DebbieN-SF]

Current version appears to use Lastname and Type of Individual even when a different type is selected (e.g. Household).

[tobiasaw34002]

Merge with #58

[waidner]

Had a brainstorming during March '23 sprint about this (see https://salesforce-external.slack.com/archives/C03E9GU0F43/p1680199911862449).

I think we should go within the MVP with a naming, which we define depending on the type used. Later we can make it more flexible. Proposal from my site that the name is created in the following way Contact.LastName & Membership__c.Type__c

If we implement this, we have to remove the logic in the quick action Contact.New_Membership.quickAction-meta.xml
Here we have created a predefined name field with the formula Contact.LastName & "- Individual Membership" => remove this predefinition.

By automating this we can close story #64