Implement the User block

[alupcosta]

Context

Implement the User block of the domain layer: Voter and Administrator, plus two context-specific administrator subclasses that store data relevant to vote weighting.

Tasks and Requirements

• Implement Voter: id and name, validated on creation.
• Implement Administrator (base):
  • Register voters (registerVoter), preventing duplicate ids.
  • Control voting session state (authorizeVotingOpening, authorizeVotingClosing, isVotingOpen).
• Implement CondominiumAdministrator (extends Administrator):
  • registerCondoMember(voter, idealFraction), storing each voter's ideal fraction.
• Implement OnuAdministrator (extends Administrator):
  • registerMemberState(voter, isPermanent), storing permanent member status.

Automated Tests (Vitest)

The test suite must cover the following scenarios:

• Valid creation of Voter and Administrator, plus error cases (missing id, empty name).
• Duplicate voter registration is rejected.
• Voting open/close state transitions, including invalid transitions (opening twice, closing when not open).
• CondominiumAdministrator correctly stores and retrieves each voter's ideal fraction.
• OnuAdministrator correctly stores and retrieves each voter's permanent member status.

[jpfrare]

Acredito que a classe de Administrador seja mais eficientemente aproveitada se não herdasse de Votante, dado que o administrador não aproveitaria o escopo e a estrutura de Votante, como o voto propriamente dito. Talvez seria mais interessante a criação das classes de forma genérica e isolada e o uso das heranças para especialização dentro do contexto de votação (e.g classe VotanteCondominio(Votante) e AdministradorCondominio(Administrador) para as votações codôminas) .

[yaesetti]

Template used was for PR. Please refactor this issue for standardization.

[yaesetti]

Since there are only 3 different cases, I think all 3 should be implemented instead of just 2.