Add two more time bounds to SearchSolutions call?

• time_bound_score - any found solution should not take longer than this to score (if called on provided input data to the search call)
• time_bound_run - any found solution should not take longer than this to fit and produce (if called on provided input data to the search call)

See dummy-ta3#13 (closed) and dummy-ta3#2 (closed) for more information. I do not see this anymore as just a question of something useful just for TA2 evaluation but in fact for TA3 as well. If you want interactive session with an user, is it really useful to quickly get solutions, but which take then days to score?