logic of when to save to history in TranslateInteractor, not sure if this is breaking SRP.
TranslateInputData also now contains a boolean representing whether to saveToHistory or not.
WordHistoryDataAccessObject now implements TranslateDataAccessInterface in addition to HistoryDataAccessInterface, so we can write to History in the translate use case.
Changes made: