configured_attr_val -> configured_attr

Summary: Similar reasoning as the previous diff, I think it should be named `configured_attr` instead of `configured_attr_val`. Also, `coerced_attr` is used for `CoercedAttr`, so I'd like to be consistent

Reviewed By: scottcao

Differential Revision: D48323665

fbshipit-source-id: 24a0a511de79ce6d1aff2ca598184ed5792078ff

app/buck2_bxl/src/bxl/starlark_defs/nodes/configured.rs

@@ -418,7 +418,7 @@ impl Serialize for StarlarkConfiguredAttr {
 
 starlark_simple_value!(StarlarkConfiguredAttr);
 
-#[starlark_value(type = "configured_attr_val")]
+#[starlark_value(type = "configured_attr")]
 impl<'v> StarlarkValue<'v> for StarlarkConfiguredAttr {
     fn get_methods() -> Option<&'static Methods> {
         static RES: MethodsStatic = MethodsStatic::new();