Rely on BCR for bringing maliput_malidrive

[francocipollone]

Summary

At the moment that #7 was created maliput_malidrive hadn't been part of the BCR so we had to use submodules

maliput-rs/maliput-sdk/build.rs

Lines 58 to 68 in 896f157

	// TODO(francocipollone): Remove this custom build once maliput_malidrive is within BCR.
	env::set_current_dir("maliput_malidrive")
	.unwrap_or_else(|_| panic!("Unable to change directory to {}", "maliput_malidrive"));
	let build_malidrive = std::process::Command::new("bazel")
	.arg("build")
	.arg("//...")
	.status()
	.expect("Failed to generate build script");
	if build_malidrive.code() != Some(0) {
	panic!("Failed to generate build script");
	}

Requisites:

• [bazel] Guarantee shared library creation for the plugin maliput_malidrive#269
• New patch release of maliput_malidrive (0.2.1)
• Update BCR with latest release (0.2.1)

Tasks:

• Add maliput_malidrive to MODULE.bazel file
• Remove maliput_malidrive submodule
• Remove custom build of maliput_malidrive in build.rs