[ROCm] bugfixing conv_parameters and activated respective test
It seems there are 2 failing tests:

```
[  FAILED  ] [Test/FusedMatMulWithBiasOpTest/1].MatMul256x128x64WithActivation, where TypeParam = Eigen::half
[  FAILED  ] [Test/FusedMatMulWithBiasOpTest/1].MatMul1x256x256WithActivation, where TypeParam = Eigen::half
```

And the errors look like:

```NOT_FOUND: No algorithm worked!``` > It seems there are 2 failing tests:
> 
> ```
> [  FAILED  ] [Test/FusedMatMulWithBiasOpTest/1].MatMul256x128x64WithActivation, where TypeParam = Eigen::half
> [  FAILED  ] [Test/FusedMatMulWithBiasOpTest/1].MatMul1x256x256WithActivation, where TypeParam = Eigen::half
> ```
> 
> And the errors look like:
> 
> `NOT_FOUND: No algorithm worked!`

OK, I will have a look at it tomorrow, possibly it depends on CUDNN version and GPU architecture (I have tested on SM 7.0 GPU). It says that CUDNN cannot not find a suitable mamul algorithm for the problem. 
 I would wait until the related PR is merged to upstream: https://github.com/tensorflow/tensorflow/pull/61941
because it applies some modifications to fused_matmul_op, then I can rebase and try running it once again. > FYI: I am using a different fix internally, we can just avoid create Eigen::half test cases on CPU.

Yes, if you have a better approach how to skip these tests, can you share it with me ?
Basically I wanted to skip those tests for which no OpKernel is available but it seems that GTEST_SKIP() does not break the test execution immediately, so there are some "patches" to make it working.. 
 @akuegel: do you know why this PR has been rejected ? I last updated it over the weekend and was hoping that the tests will run fine now.. Can you explain what you mean with rejected? This (i.e. the version I had approved, + the fixes I added) got merged 46 minutes ago. It took a while because I needed internal approvals from US-based people, so they happened after my working hours. And this morning I was OOO as well. ah sorry, I was confused by this message: 
```
[PR Queue] automation moved this from Approved by Reviewer to Closed/Rejected [1 hour ago]
```
many thanks for the help !
 It seems my idea of a fix doesn't work, because we seem to run the _cpu version of the test also with --config=cuda. Some followup might be needed, maybe also a temporary revert. OK, then I guess the only way is to check for the errors at runtime.. 

For example, in Python there are exceptions, and some tests do it in this way:
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/kernel_tests/nn_ops/depthwise_conv_op_base.py#L377-L387

In C++, I also tried to selectively skip subtests depending on tsl::Status() message but without exceptions it's more cumbersome.. I think I found a solution, adding the tag no_cuda_on_cpu_tap should avoid that the test is automatically run on CPU with --config=cuda. That should be good enough.
This is bugfix in conv_parameters.cc originally appeared in https://github.com/ROCmSoftwarePlatform/tensorflow-upstream/pull/2000 and then in the follow-up PR: https://github.com/tensorflow/tensorflow/pull/61941

As requested, I am submitting this bugfix as a separate PR. 
I also had to extend the tests for Eigen::half datatype and 'Tanh' and 'Sigmoid' activations
since in this case fused matmul uses the CuDNN fallback which, in its turn, 
uses MatmulParameters constructor (from tensorflow/core/util/autotune_maps/conv_parameters.cc).

Additionally, I also removed MatmulParameters class from tensorflow/core/kernels/matmul_op.h which is a deadcode (to remove any confusions).

@akuegel: could you please review this as this is a follow up to https://github.com/tensorflow/tensorflow/pull/61941 PR ?