Updates needed for mtbs data

[jhamman]

I've noticed a few things with our MTBS dataset that should be corrected:

1. The processed conus and ak 4km datasets are the same (both conus domain)
2. The processed dataset uses a resolution key of 4000 instead of 4000m. This should be updated to match the rest of our catalog conventions.

data/catalogs/mtbs.yaml

Lines 35 to 39 in 9337820

	resolution:
	description: Pixel resolution in meters
	type: str
	default: "4000"
	allowed: ["4000"]

[freeman-lab]

@jhamman I fixed the 4000 -> 4000m thing in our files and updated the catalog, still need to reprocess ak