Use common job class naming convention

When creating scheduled jobs, it is essential to give meaningful and descriptive names to those jobs to help you and other developers to understand their purpose and functionality.

• Use a clear and descriptive name that reflects the job's purpose.
• Avoid using generic names that do not convey any information about the job. For example, A meaningful name for a scheduled job that cleans up expired alarms from a database could be "ExpiredAlarmCleanerJob". These names accurately reflect the job's purpose and make it clear to other developers what the job does.
• Use a naming convention that is consistent with your project's naming conventions. We can use PascalCase for job naming throughout all projects.
• Use full words instead of abbreviations to make the name more readable. If you must use an abbreviation, make sure it is commonly understood.