State checking for extending abstract classes

Currently, reusing state refinements from an abstract superclass in a concrete class is not fully implemented, and gives an error like the one below.

Example for abstract class java.net.URLConnection:

@ExternalRefinementsFor("java.net.URLConnection")
@StateSet({"setup", "connected"})
public interface URLConnectionRefinements {
 
    @StateRefinement(to="setup(this)")
    public void URLConnection(URL url);

    @StateRefinement(from="setup(this)")
    public void setDoInput(boolean doinput);

    @StateRefinement(from="setup(this)", to="connected(this)")
    public void connect();

    @StateRefinement(from="connected(this)")
    public Object getContent();
 
}

Extended in class URLExt:

class URLExt extends URLConnection{

    public URLExt(URL url){
        super(url);
    }

    @Override
    public void connect() throws IOException {
        // TODO Auto-generated method stub
        throw new UnsupportedOperationException("Unimplemented method 'connect'");
    }
    
}```

Tested in:
```java
class Testurl {
    void test() throws URISyntaxException, IOException {

        URLExt u = new URLExt(new URI("http://example.com").toURL());
        u.setDoInput(false); // should not be an error but it is 
        u.getContent(); // should be an error

    }
}

Reproduza o relatório usando as anotações URLConnectionRefinements, URLExt e o exemplo Testurl. Comece rastreando como os refinamentos de estado herdados de java.net.URLConnection são verificados quando métodos são invocados em URLExt. Está concluído quando setDoInput(false) é aceito, enquanto getContent() é rejeitado porque o objeto ainda não atingiu o estado conectado.