Director Name Change - research name comparison

### Director Name Change - research name comparison
## Description:
RESEARCH ONLY
Result of this story is to determine what (if any) solution exists to be able to understand difference between legal name change and changed person entirely. At the end of this task, if it is deemed do-able, be able to estimate work needed to implement.

From parent story:
***Nice to have - time box to research for 1 hour and if its doable in 2 days we may add it
When I change the legal name and it is seems like the name is a full change which may indicate that the user is using this function to add a director
Then we warn the user that "it looks like you might not be filing legal name change?" Confirm this is a legal name change

### Potentially useful NPM package that scores the similarity between strings:
https://www.npmjs.com/package/string-similarity

**Dependencies**

**Acceptance Criteria**

**Validation Rules**

Ready to Build (DoR):
- [ ] Stakeholders have approved
- [ ] User story completed
- [ ] What are the dependencies
- [ ] Validation rules defined (UI, Data, Role-Action)
- [ ] Is a formal UAT required

Acceptance / DoD:
- [ ] Design / Solution accepted by Product Owner
- [ ] Acceptance criteria has been defined (happy path, known sad paths)
- [ ] Test coverage acceptable
- [ ] Peer Reviewed
- [ ] Accessibility reviewed and acceptable [checklist](https://github.com/bcgov/entity/docs/coding-standards/accessibility.md)
- [ ] UX Approved
- [ ] PR Accepted
- [ ] Production burn in completed

Start by reviewing the parent story and the proposed string-similarity NPM package to determine whether name comparison can distinguish a legal name change from adding a different director. Document whether the approach is feasible and estimate the implementation work; no files or tests are identified in the issue.

Written by the indexing model from the issue text.