If you always work with the same default catalog in your workspace, it is easier to link that catalog as default catalog of that workspace. See https://docs.databricks.com/aws/en/catalogs/default
If you do this, you can mention tables just by <schema>.<name> and the catalog will be the default one. To use a different default catalog per environment would be achieved by using a different workspace for each environment, which is a common setup that ensures isolation of environments.

Of course, this is no viable solution if you want to use a different catalog for certain jobs or workflows. In that scenario the above answer of Jaya Shankar G S is a very practical option: to associate the default catalog to your compute cluster, of which you may define a different one for each catalog you would like to work on.