799 sync militia party component

[georgyrudnev]

PR Checklist

Please check if your PR fulfills the following requirements:

• [ ] All new classes have class-level documentation comments, if there are any at all
• [ ] Tests for the changes have been added (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• [ ] Bug fix (non-breaking change that fixes an issue)
• [X] New feature (non-breaking change that adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Build related changes
• [ ] CI related changes
• [ ] Documentation update
• [ ] Other... Please describe:

What is the current behavior?

Settlement property inside MilitiaPartyComponent is not synced

What is the new behavior?

Resolves #799

Sync´s Settlement property inside militiaPartyComponent which seems to only be set during ctor

Other information

[georgyrudnev]

MilitiaPartyComponent constructor on the server is not triggering the Settlement property setter patch as expected. Client-side instance creation skipping the constructor is working as designed. Issue lies in serveside behavior, where the settlemt property setter should be called during construction triggering our prefix patch for syncing the property. This is not happening preventing proper synchronization of the Settlement property to clients. Need to investigate why server-side setter is not triggering our patch during the component's construction.

[garrettluskey]

Anyway to use autosync instead?