feat: Adds the temporal fusion transformer (TFT) forecasting job

[mikelawrence-google]

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• Ensure the tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)

Fixes b/239609625 🦕

[conventional-commit-lint-gcf]

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot
https://conventionalcommits.org/

[mikelawrence-google]

@sasha-gitg Hi there, I need a little help and I see you've done a lot of work in this repo. Do you often have this presubmit issue with pytest like,

_____________________________ ERROR collecting gw2 _____________________________ Different tests were collected between gw3 and gw2. The difference is: 

I don't think my PR has done anything particularly wild... I'm not sure how to fix this. Any ideas? If you think someone else might be better to ask, feel free to let me know

[sasha-gitg]

@mikelawrence-google Looks like an issue with python-xdist and @pytest.mark.parametrize with a set: pytest-dev/pytest-xdist#149

Try changing back to list or following the sorted recommendation in the issue.

[mikelawrence-google]

Thanks for taking a look, @sasha-gitg and @sararob. I thought it was more related to build infrastructure, but it was indeed the set vs list issue. My team is waiting on some documentation before we can merge, but will get the review going

[geraint0923]

Thanks for adding the SDK support for TFT!

[sasha-gitg]

When will TFT be released? We should hold merging until it is released.

[mikelawrence-google]

The backend is ready, we are just waiting for documentation and some UI pieces. It's completely usable though. My TL suggested we merge it ahead of time with the understanding that customers can use it, just without the GA guarantees at launch time (~1 month out). What do you think?

[sararob]

We are doing maintenance on our repo starting today and need to close all open PRs. When this is done next week, you'll be able to open a new PR.