[NOREF]Constrain mto solution poc fields

[StevenWadeOddball]

NOREF

Description

1. POC email and POC name are now not editable if you make a custom solution
2. Milestone and solutions sourced from common options now update correctly, and don't attempt to set name and type

How to test this change

1. Create a solution from a common solution
2. attempt to edit the poc info.
3. Confirm the action fails.
4. Edit other information. Confirm it passes
5. Confirm you can update a milestone made from the common milestone library.

PR Author Checklist

• I have provided a detailed description of the changes in this PR.
• I have provided clear instructions on how to test the changes in this PR.
• I have updated tests or written new tests as appropriate in this PR.
• Updated the Postman Collection if necessary.

PR Reviewer Guidelines

• It's best to pull the branch locally and test it, rather than just looking at the code online!
• When approving a PR, provide a reason why you're approving it
  • e.g. "Approving because I tested it locally and all functionality works as expected"
  • e.g. "Approving because the change is simple and matches the Figma design"
• Don't be afraid to leave comments or ask questions, especially if you don't understand why something was done! (This is often a great time to suggest code comments or documentation updates)
• Check that all code is adequately covered by tests - if it isn't feel free to suggest the addition of tests.

[ClayBenson94]

Approving! Had some suggestions about potentially improved logging, and maybe a suggestion for the SQL constraint, but nothing that should stop this from merging as-is if you want!

[OddTomBrooks]

I have no significant feedback. The changes are succinct and self-evident.