Creating new jobs and changing guid does not create new job in admin

Description

When you created your own EmptyWastebasketJob, gave it a new guid and started the job in admin, the job had a translated name instead of the one that was set by the LanguagePath = "/admin/databasejob/wastebasket" attribute. Even if you removed the attribute and changed the DisplayName, the job still had the translated name.

If you then removed all attributes except for guid and DisplayName, and gave the job a new guid, it resulted in no new job registered; just the same job with the same name.