Update component history early (maybe by changing CI/CD which support custom cron time)

[iamsauravsharma]

Currently component history is updated about 3:30 AM GMT which is more than 3 hours slow then when new nightly is available. So instead of using travis which doesn't allow to set time when cron job is ran it may be better to change to other CI/CD may be GitHub Actions or Azure Pipelines which both support custom cron time. Currently if some one need update about component availability they have to wait for 3 hours to get new information instead of getting old information which may not be correct.

[wongsyrone]

#35

[sagudev]

When it should run? Currently it runs at 00:10 UTC every day. Maybe we can run it every morning hour, to catch nightly?