Make entity path parsing infallible by default

Closes #3393

For the Python and Rust SDK, any string is now a valid entity path,
though perhaps not the one you where expecting. A warning is printed
if the format is not the normalized format.

For C/C++ I opted to still use the strict parsing for now.
We can revisit that later.

crates/re_data_store/src/instance_path.rs

@@ -112,7 +112,7 @@ fn test_parse_instance_path() {
     assert_eq!(
         InstancePath::from_str("world/points[#123]"),
         Ok(InstancePath {
-            entity_path: EntityPath::from_str("world/points").unwrap(),
+            entity_path: EntityPath::from("world/points"),
             instance_key: InstanceKey(123)
         })
     );

crates/re_log_types/src/path/entity_path.rs

@@ -210,19 +210,17 @@ impl From<&[EntityPathPart]> for EntityPath {
     }
 }
 
-#[allow(clippy::fallible_impl_from)] // TODO(#3393): we should force users to handle errors instead, and have a nice macro for constructing entity path
 impl From<&str> for EntityPath {
     #[inline]
     fn from(path: &str) -> Self {
-        path.parse().unwrap()
+        EntityPath::parse_forgiving(path)
     }
 }
 
-#[allow(clippy::fallible_impl_from)] // TODO(#3393): we should force users to handle errors instead, and have a nice macro for constructing entity path
 impl From<String> for EntityPath {
     #[inline]
     fn from(path: String) -> Self {
-        path.parse().unwrap()
+        EntityPath::parse_forgiving(&path)
     }
 }