stop packing future variable to avoid tsan data race warnings

[DmitriyMusatkin]

Issue #, if available:

Description of changes:
future bitpacks several variables into uint32
https://github.com/awslabs/aws-c-io/blob/main/source/future.c#L54

tsan will complain if those variables are accessed from different threads.
this pr fixes the data race from aws_future_impl_get_result_by_move updating owns_data variable and aws_future_impl_set_error reading is_done, by unpacking the variables.

aws-c-io/source/future.c

Line 219 in 25faa8d

future->owns_result = false;

aws-c-io/source/future.c

Line 302 in 25faa8d

bool first_time = !future->is_done;

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.66%. Comparing base (25faa8d) to head (bc3db4d).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #741   +/-   ##
=======================================
  Coverage   78.66%   78.66%           
=======================================
  Files          30       30           
  Lines        6374     6374           
=======================================
  Hits         5014     5014           
  Misses       1360     1360           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[graebm]

fix & ship