Fix duplicated tweet

[wildan3105]

Is your feature request related to a problem? Please describe.
For day-1

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

[wildan3105]

This is attempting to tweet a match that's about to begin in 24 hours
2024-02-16T06:01:51.770127+00:00 app[worker.1]: There's an error when calling twitter API. Details: AxiosError: Request failed with status code 403
2024-02-16T06:01:54.717345+00:00 heroku[scheduler.2532]: Process exited with status 0

Re-open this issue to find the long-term fix for the above error response from Twitter's API.

[wildan3105]

Idea

• For each match found and valid, store the data in the following format (match-fetcher.ts) (Refactor/change match fixtures strategy #102 ):

[
	{
		"participants": "Club A vs Club B",
		"tournament": "Champions League",
		"stadium": "Club A stadium",
		"date_time": "" // date time of the reminder i.e. match - 24 hours
	},
	{
		"participants": "Club A vs Club B",
		"tournament": "Champions League",
		"stadium": "Club A stadium",
		"date_time": "" // date time of the reminder i.e. match - 1 hour
	}
];

• Add hours_to_match in redis data (add hours_to_match in redis data #103 )
• Fetch match and sort by the closest date to now() (DESC by reminder_date) and only return 1 match (match-reader.ts) (refactor: fetch matches and sort by reminder_time closest to now #105)
• If (diff(reminder_date - now)) <= 1, publish match (Refactor/publish reminder with new strategies #108 )
• Modify the subscriber accordingly (refactor(subscriber): remove extra checking of hours_to_match #110 )
• Deploy the base branch to heroku