[AIRFLOW-5553] MySqlToGoogleCloudStorageOperator: Bytes value check done based on the type of the variable
diff --git a/airflow/operators/mysql_to_gcs.py b/airflow/operators/mysql_to_gcs.py
index fef2c20b05f12..d7c07c81936b0 100644
--- a/airflow/operators/mysql_to_gcs.py
+++ b/airflow/operators/mysql_to_gcs.py
@@ -119,6 +119,6 @@ def convert_type(self, value, schema_type):
             return value.total_seconds()
         if isinstance(value, Decimal):
             return float(value)
-        if schema_type == "BYTES":
+        if isinstance(value, bytes) or schema_type == "BYTES":
             return base64.standard_b64encode(value).decode('ascii')
         return value

Make sure you have checked _all_ steps below.

### Jira

- [x] My PR addresses the following [Airflow Jira](https://issues.apache.org/jira/browse/AIRFLOW) issues and references them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
  - https://issues.apache.org/jira/browse/AIRFLOW-5553
  - In case you are fixing a typo in the documentation you can prepend your commit with \[AIRFLOW-XXX\], code changes always need a Jira issue.
  - In case you are proposing a fundamental code change, you need to create an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)).
  - In case you are adding a dependency, check if the license complies with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x).

### Description

- [x] Here are some details about my PR, including screenshots of any UI changes:
Changed the condition to decode bytes values so they will now be dealt with without having to specify a BQ schema

### Tests

- [x] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
It's a trivial one line change adding a single condition to do the same task that had been done before.

### Commits

- [x] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
  1. Subject is separated from body by a blank line
  1. Subject is limited to 50 characters (not including Jira issue reference)
  1. Subject does not end with a period
  1. Subject uses the imperative mood ("add", not "adding")
  1. Body wraps at 72 characters
  1. Body explains "what" and "why", not "how"

### Documentation

- [x] In case of new functionality, my PR adds documentation that describes how to use it.
  - All the public functions and the classes in the PR contain docstrings that explain what it does
  - If you implement backwards incompatible changes, please leave a note in the [Updating.md](https://github.com/apache/airflow/blob/master/UPDATING.md) so we can assign it to a appropriate release
