[Website] Remove support for triggering GitHub Actions apache/arrow-site website deployment workflow when pushing to master

[asfimport]

This is a follow up to ARROW-15694.

Once Apache Infra switches the default Git branch from master to main in apache/arrow-site, we should completely remove support for triggering the deploy.yml CI workflow on a push to master.

This should be straightforward and would involve removing master from the .github/workflows/deploy.yml push trigger condition.

Reporter: Kevin Gurney / @kevingurney

_{Note: This issue was originally created as ARROW-15988. Please see the migration documentation for further details.}

[asfimport]

Todd Farmer / @toddfarmer:
This issue was last updated over 90 days ago, which may be an indication it is no longer being actively worked. To better reflect the current state, the issue is being unassigned. Please feel free to re-take assignment of the issue if it is being actively worked, or if you plan to start that work soon.

[kevingurney]

take

[kevingurney]

I verified that the apache/arrow-site deployment workflows in .github/workflows/deploy.yml are already prepared to work with "main" or "master".

See line 23 and line 51.

Note that the Jira issue ARROW-15988, which is referred to in the comments on these lines, is now being tracked as #31412 (this issue) in GitHub Issues. However, this issue can't be addressed until the default branch has been renamed to "main". Therefore, I'll follow up with a PR to address this as soon as Apache INFRA has renamed the default branch of the apache/arrow-site repo to "main".

[jorisvandenbossche]

The master->main branch rename is now also done for the apache/arrow-site repo, so you can go forward with this

[kevingurney]

Thanks, @jorisvandenbossche. I'll proceed with the changes.

[kevingurney]

I don't think I have the permissions to change it, but I think this issue should be part of the [Website] component rather than the [Dev] component.

[kou]

Changed the component.