calling prop_def twice on a task creates multiple properties with the same name

[jacobe90]

see this test for behavior

a-better-notion/client/src/mid.rs

Lines 861 to 879 in 55faba7

	async fn test_prop_def_twice() {
	let (server, mut state, mut receiver, view_key) = test_init().await;
	let view = state.view_get(view_key).unwrap();
	assert_eq!(view.name, "Main View");
	let mut tasks = view.tasks.as_ref().unwrap().iter().cloned().collect::<Vec<TaskKey>>();
	tasks.sort(); // make keys are in sorted order
	// assign a date to tasks[0]
	let name_key = state.prop_def_name("random property");
	let old_prop_key = state.prop_def(tasks[0], name_key, TaskPropVariant::Date(NaiveDate::from_ymd_opt(2016, 7, 8).unwrap().into())).unwrap();
	let prop_key = state.prop_def(tasks[0], name_key, TaskPropVariant::String(String::from("j"))).unwrap();
	let old_prop_ref = &state.props[old_prop_key];
	let new_prop_ref = &state.props[prop_key];
	// both should have type "string"
	assert_eq!(old_prop_ref.type_string(), new_prop_ref.type_string());
	}