Preparing N1 S3 build bucket and OIDC

[andrei-near]

These workflows will build binaries and push them into n1 build bucket:
n1.build.nearprotocol.com

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.49%. Comparing base (7d0e3d7) to head (919f1e9).
Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #11987      +/-   ##
==========================================
- Coverage   71.49%   71.49%   -0.01%     
==========================================
  Files         810      810              
  Lines      164037   164037              
  Branches   164037   164037              
==========================================
- Hits       117283   117273      -10     
- Misses      41671    41674       +3     
- Partials     5083     5090       +7     

Flag	Coverage Δ
backward-compatibility	0.23% <ø> (ø)
db-migration	0.23% <ø> (ø)
genesis-check	1.33% <ø> (ø)
integration-tests	38.40% <ø> (-0.01%)	⬇️
linux	71.25% <ø> (-0.01%)	⬇️
linux-nightly	71.07% <ø> (+<0.01%)	⬆️
macos	54.36% <ø> (+0.01%)	⬆️
pytests	1.60% <ø> (ø)
sanity-checks	1.40% <ø> (ø)
unittests	65.58% <ø> (-0.01%)	⬇️
upgradability	0.28% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[nagisa]

LGTM given my surface-level understanding of the specifics here. That said, some thoughts I had reading this which I think are worth writing down:

1. Is N1 specific stuff really something that should live in this repository. Or said different way, if NF decides they want their own bucket, do we get a 3rd copy of scripts and workflows? What if some other entity decides they want a slice of this pie too?
2. For workflows specifically duplication could be avoided with matrices.

[andrei-near]

LGTM given my surface-level understanding of the specifics here. That said, some thoughts I had reading this which I think are worth writing down:

1. Is N1 specific stuff really something that should live in this repository. Or said different way, if NF decides they want their own bucket, do we get a 3rd copy of scripts and workflows? What if some other entity decides they want a slice of this pie too?
2. For workflows specifically duplication could be avoided with matrices.

N1 bucket is a temporary situation. Another PR will follow-up soon with more details and revert of this change.