Architect module | Delete Architect Feature

## Architect Delete Process

### User Story
- As an architect, I want the ability to deactivate my account in the application.
- Deactivating my account ensures that my personal information is no longer accessible or displayed.

### Task: Implement Architect Account Deactivation
- [ ] Develop the Data Access Object (DAO) Layer for architect account deactivation.
- [ ] Implement the Service Layer to handle the architect account deactivation process.
- [ ] Write Test Cases to validate the correctness of the account deactivation functionality.
- [ ] Ensure that the test cases cover various scenarios, including successful deactivation.
- [ ] Verify that all test cases pass successfully and produce the expected outcomes.
- [ ] Enhance code clarity by adding concise comments to explain complex logic.

### DAO:
- [ ] deleteArchitect

### Service:
- [ ] deleteArchitect

### Test:
- [ ] testDeleteArchitectSuccess
- [ ] testDeleteNonExistingArchitect
- [ ] testDeleteArchitectWithInvalidEmailFormat

### Estimation
- [ ] 1 hrs

### Flow
```mermaid
graph TD
A[(Start)] --> B([Select Account to Deactivate])
B --> |Confirm Deactivation| C([Deactivate Account])
C --> |Account Deactivated| I([Deactivation Successful])
B --> |Cancel Deactivation| D([Cancel Deactivation])
D --> I
C --> |Deactivation Failure| E{{Error in Deactivation}}
E --> F([Log Error])
F --> G([Display Error Message])
G --> H[(End)]
E --> G
```