Those 302 indicate that your pages are redirected. When you switch from HTTP to HTTPS, that is what you want. You want your site from HTTP to HTTPS you want visitors and search engine bots to get redirected to the HTTPS site.
There is no need to remove any of these codes from that report in Google Search Console. When Google reports that it finds hundreds of redirects, you only need to do something if you are not expecting those pages to redirect.
You should change those redirects from "302 temporary" redirects to "301 permanent" redirects. Once you make the change to HTTPS, you shouldn't ever have to go back. Semantically, "permanent" makes more sense. 301 redirects are better for SEO because search engines pass link juice across them more reliably. 302 redirects have the potential to cause ranking problems associated with this protocol change. 301 redirects are also better cached by browsers. Users that type your domain name into their browsers regularly will get a faster experience with 301 redirects. Their browser won't need to contact your server each time.
I'm not sure exactly how you implemented the redirects. You'll need to figure out how to change them to permanent redirects. The two most common ways are with a rewrite rule and with a Apache redirect directive. With a rewrite rule, you would change
RewriteRule ... [R] to
RewriteRule ... [R=301]. With a redirect directive you would change
redirect / https://... to
redirect permanent / https://....
The other thing that you should do is add your
https://example.com/ property to Google Search Console. Your
http:// property isn't going to show meaningful data from now on. Search analytics will now move over to the HTTPS property. Index and crawl reports will be more meaninful on the HTTPS property. You'll need to resubmit any sitemaps you may have submitted to the HTTPS property version.
You can keep both the HTTP search console property around. It isn't hurting anything. You could also consider adding
www. and no-www variants. I recommend adding four properties for most sites. All the combinations of http, https, www, and no-www.
302. Therefore I'd suggest checking your server's config files (e.g., .htaccess) or server application for related code (i.e., you should see "302" in the code). From there you might be able to determine what its purpose was, and if you want to change that to something else (like a