[Component amendment]: Do input fields need an active state?

## Input

Should inputs in general have an active state? From my limited research, it seems unnecessary.
- What happens when you press inside an input? Usually nothing, as there is no action atrtached to inputs
- Carbon and Material do not seem to have one:

## Visual

The proposal here is to keep the default state and remove the current active state, unless there is a clear reason for it to exiest.

## Context

In what context does your amendment solve a problem?

Start by locating the Input component styles and reviewing how its active state is currently represented. Compare the existing visual behavior with the proposal and decide whether removing the state is justified; done means the amendment has a clear decision and the component visuals match it.

Written by the indexing model from the issue text.