First of all, thanks again for the amazing work on `formik`, I've recently upgraded it from 0.* to 1.3 without breaking changes 😲!

I think this package brings not so much value considering more generic alternatives, like: https://ui.reach.tech/component-component

I propose to deprecate this redirecting the new users to the alternatives!

## Comparison
```javascript
// withFormikEffect.js
import React from 'react'
import ReactDOM from 'react-dom'
import {Formik, Form, Field} from 'formik'
import {Effect} from 'formik-effect'

const App = () => (

const rootElement = document.getElementById('root')
ReactDOM.render(, rootElement)
```
vs
```javascript
// withComponentComponent.js
import React from 'react'
import ReactDOM from 'react-dom'
import {Formik, Form, Field} from 'formik'
import Component from '@reach/component-component'

const App = () => (

const rootElement = document.getElementById('root')
ReactDOM.render(, rootElement)
```

The difference is minimal and u can do it in other ways also (for example passing only the formikBag props you want to `Component`)

The issue does not name files, tests, or a concrete implementation plan. Review the package entry points and release metadata, then assess the proposed deprecation and the @reach/component-component comparison; done would require a maintainer-approved deprecation path and updated guidance.

Written by the indexing model from the issue text.