[jsk_fetch_startup] Use email address instead of yaml for smach_to_mail

[tkmtnt7000]

This change depends on #1588 .
We use rosparam instead of yaml file to set email information.

[knorth55]

this is not good because, it only supports fetch1075.
how about generating email_topic yaml in CMakeLists.txt?
like this:

jsk_robot/jsk_fetch_robot/jsk_fetch_startup/CMakeLists.txt

Lines 78 to 91 in 68ae4be

	macro(configure_dialogflow_hotword_yaml dname)
	set(FETCH_NAME ${dname})
	if (${FETCH_NAME} STREQUAL "fetch15")
	set(ROBOT_NICKNAME_KANA "ヘンゼル")
	set(ROBOT_NICKNAME_HIRA "へんぜる")
	configure_file(${CMAKE_CURRENT_SOURCE_DIR}/config/dialogflow_hotword.yaml.in
	${CMAKE_CURRENT_SOURCE_DIR}/config/${FETCH_NAME}_dialogflow_hotword.yaml)
	elseif (${FETCH_NAME} STREQUAL "fetch1075")
	set(ROBOT_NICKNAME_KANA "グレーテル")
	set(ROBOT_NICKNAME_HIRA "ぐれーてる")
	configure_file(${CMAKE_CURRENT_SOURCE_DIR}/config/dialogflow_hotword.yaml.in
	${CMAKE_CURRENT_SOURCE_DIR}/config/${FETCH_NAME}_dialogflow_hotword.yaml)
	endif()
	endmacro(configure_dialogflow_hotword_yaml)

jsk_robot/jsk_fetch_robot/jsk_fetch_startup/CMakeLists.txt

Lines 95 to 96 in 68ae4be

	configure_dialogflow_hotword_yaml(fetch15)
	configure_dialogflow_hotword_yaml(fetch1075)

[tkmtnt7000]

Thank you very much for reviewing. I mistakenly set email address without thinking about fetch1075 and fetch15.
I think it may be good to generate a email config file from CMakeLists.txt.

[tkmtnt7000]

Sorry for force-pushing...
Config yaml file is generated when we build workspace.

[k-okada]

@tkmtnt7000 @knorth55
Sorry, I did not look the changes of this PR carefully, I originaly intend to use rosparam directly within launch file, instead of using yaml file,

see
k-okada@37b71ce, may be this is too complex....

[knorth55]

receiver name should be different from the hostname, but we can write the address directly.
another point is that we cannot share the address information if we directly write it on launch file.
but i dont know if it is necessary.