Localization Extraction Enhancement

1. Dynamic Questionnaire Translatable Fields

Currently, only text fields are translated. This is defined in the command code.
This should be dynamic as more fields could be translatable, i.e display field. Implementation
[x] Create a FCTConstants.java file and add a questionnaireTranslatables array constant in the FCTConstants.java file.
[x] Specify text and display fields in the array
[x] Modify questionnaire extraction code to extract all fields in the questionnaires whose key is in the questionnaireTranslatables

2. Add Extraction Type flag to the translate command

This will be used to distinguish between questionnaire extraction and configs extraction Implementation
[x] Add -et flag that accepts either -et questionnaire or -et config
[x] Add condition to the translate command that switches to either questionnaire or config extraction based on this flag.
[x] If this flag is not provided, check the last part of the directory provided, if it ends with questionnaires perform questionnaires extraction, if it ends with configs perform configs extraction.

e.g

fct translate -m extract -et config -rf path/to/project/configs

3. Full project translatable fields extraction

Allow for users to only provide path to project and perform extraction of both configs and questionnaires in the project. e.g
```
fct translate -m extract -rf  path/to/project
```
[x] Update Documentation of commands on efsity READ ME

onaio / fhir-tooling